-
Notifications
You must be signed in to change notification settings - Fork 1
fix: vscode_parser incremental append-only parsing (#764) #768
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
Open
microsasa
wants to merge
6
commits into
main
Choose a base branch
from
fix/764-vscode-incremental-parse-1bb1b0d20398400d
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+367
−65
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
d454f20
fix: vscode_parser incremental append-only parsing (#764)
microsasa 6f3adb4
fix: address review comments
microsasa 0d6b173
fix: address review comments
microsasa eec3879
fix: address review comments
microsasa e3299c4
fix: address review comments
microsasa a07b4fc
fix: add tests for TOCTOU truncation paths to satisfy diff-coverage
microsasa 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
Some comments aren't visible on the classic Files Changed page.
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
Oops, something went wrong.
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.
The
_get_cached_vscode_requestsdocstring says it detects append-only growth by comparingst_sizeto the “cached size” and treats replacement asnew size < cached size, but the implementation actually compares the currentst_sizeagainst the cachedend_offset(safe parse boundary). Update the wording to referenceend_offset(and that truncation/replacement is detected whenst_size < end_offset) so the docs match behavior, especially when a previous parse stopped before EOF due to a partial line.