-
-
Notifications
You must be signed in to change notification settings - Fork 31
feat(lsp): track document versions and include in publish_diagnostics #544
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
3229c52
feat(lsp): track document versions and include in publish_diagnostics…
avifenesh b3aa586
fix(lsp): address review findings for document version tracking (#478)
avifenesh 5a050e7
fix(lsp): atomize version+content updates, fix version tracking on em…
avifenesh 625645d
fix(lsp): correct misleading comment about lock drop order
avifenesh 18f07fe
docs: add changelog entry for LSP document version tracking (#478)
avifenesh 714476a
fix(lsp): apply rustfmt formatting to LSP backend code
avifenesh 6872268
fix(lsp): address race condition and misleading comments in version t…
avifenesh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
validate_from_content_and_publishreads the document version aftershould_publish_diagnosticsreturns. A concurrentdid_changecan happen between those awaits, causing stale diagnostics (computed from old content) to be published with the newer version, which defeats client-side stale-result suppression.Consider capturing
(content_arc, version)together under a single lock acquisition (or a combined struct/lock for content+version) and re-checking that the current content still matches before publishing, then publish using the version associated with that same snapshot.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in commit 6872268. Now capturing version atomically with content snapshot (lines 210-211 in backend.rs). The captured_version is used at publish time, ensuring diagnostics are published with the version matching the content they were validated from, not a newer version from concurrent did_change events.