Bug 442133

Summary:	LSP reporting stale errors after file is reloaded externally
Product:	[Applications] kate	Reporter:	Denis Lisov <dennis.lissov>
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	waqar.17a
Priority:	NOR
Version First Reported In:	21.08.1
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Denis Lisov 2021-09-07 15:13:18 UTC

STEPS TO REPRODUCE
1. Open a file in some repository that has LSP support
2. Edit it, introducing a bug that LSP highlights, and save
3. Outside Kate, revert it to the previous state in the way corresponding to the VCS used
4. Return to Kate and allow it to reload the externally modified file

OBSERVED RESULT
Kate is still showing old error positions corresponding to the pre-revert state

EXPECTED RESULT
Kate should propagate the new stat of the file to the language server so that its output matches the displayed state of the file.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo, Frameworks 5.85.0, Kate 21.08.1

Comment 1 Waqar Ahmed 2021-10-11 07:20:12 UTC

Which LSP?

> Kate should propagate the new stat of the file to the language server

Kate does that.

Try pressing F5, and if the errors are still being highlighted, then it is most likely a bug in the server.

Comment 2 Denis Lisov 2021-10-11 07:28:53 UTC

(In reply to Waqar Ahmed from comment #1)
> Which LSP?

RLS (Rust)

> > Kate should propagate the new stat of the file to the language server
> 
> Kate does that.
> 
> Try pressing F5, and if the errors are still being highlighted, then it is
> most likely a bug in the server.

The errors are still being highlighted immediately after a revert. F5 does not help, but a small edit (like adding a space to the last line) causes them to disappear. Does the propagation on reload and propagation on edit happen in different ways?..

Comment 3 Waqar Ahmed 2021-10-11 11:55:42 UTC

Weird that F5 doesn't help since it reloads everything about the doc.

Anyways, for the warnings to disappear, that is expected behaviour but yeah could be improved.

Comment 4 Waqar Ahmed 2021-12-07 05:35:37 UTC

Closing as doesn't seem like a bug in our client + rust-analyzer is the prefered way to go these days.