-
Notifications
You must be signed in to change notification settings - Fork 15
fix(check): scope signature-change detection to exported symbols #1792
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
carlos-alm
wants to merge
5
commits into
main
Choose a base branch
from
fix/titan-check-signature-scope
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.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
7f3b2cb
fix(check): scope signature-change detection to exported symbols + fi…
carlos-alm 2a58531
fix(check): track new-side diff lines symmetrically with old-side (#1…
carlos-alm d30ffae
Merge branch 'main' into fix/titan-check-signature-scope
carlos-alm c4f8cea
fix: guard +++ /dev/null deletion header in parseDiffOutput (#1792)
carlos-alm 52fdb65
Merge branch 'main' into fix/titan-check-signature-scope
carlos-alm 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
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.
+++ /dev/nullbypasses all filters and corrupts the previous file's rangesWhen a deleted file follows a modified file in the diff, the
+++ /dev/nullheader is not caught by any guard:isDevNullSourceLineonly matches--- /dev/null, andextractNewFileNamerequires ab/prefix. The line falls through totracker.consume, whereline.startsWith('+')evaluates totrue, so it is recorded as an added source line inchangedRangesfor the previous file. The subsequent@@ -N,M +0,0 @@hunk header from the deleted file then flushes and restarts the tracker under the wrong file, causing the deleted file's removed lines to land inoldRangesof the preceding file.Before this PR,
pushHunkRangesreceived the same line but theHUNK_REmatch failed, so it silently returned — effectively a safe no-op. The newconsumepath actively processes any+-prefixed line, introducing the regression. The doc comment onconsumestates that`+++`headers are "already filtered out by the caller" — that holds for+++ b/…but not for+++ /dev/null. The fix is to add a symmetric guard inparseDiffOutputbeforetracker.consumeis reached:The test suite covers new-file creation (
--- /dev/null→+++ b/…) but has no test for file deletion (--- a/…→+++ /dev/null), so this path is currently uncovered.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 — added an explicit guard for
+++ /dev/null(file-deletion header) right after theextractNewFileNamecheck. It's notb/-prefixed so it was falling through totracker.consume, which read the leading+and recorded it as an added line under whichever file preceded it in the diff — corrupting that file'schangedRangesand then misattributing the deleted file's removed lines to it via the next hunk header. The new guard flushes and clearscurrentFileon+++ /dev/nullinstead, so the deleted file's hunk body is skipped entirely (its nodes are purged from the DB during the rebuild anyway, so there's nothing to check it against). Added a regression test ("a deleted file does not corrupt the ranges of the preceding file") covering exactly this ordering.Separately, filed #1806 for a related but out-of-scope gap I noticed while fixing this: even with ranges tracked correctly,
checkNoSignatureChangescan never flag a fully-deleted file's exported symbols, since the DB lookup is against post-change state where the file's nodes have already been purged. That's a pre-existing limitation of the query approach, not something introduced by this PR, so it needs its own design rather than a fix here.