Repository navigation
fix(server): restore checkouts from leftover worktree folders #24398
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
Closed
+106
−3
Closed
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
1b2e430
test(server): tests reproduce issue 24390
juliusmarminge 3d76e10
fix(server): a managed worktree left with only node_modules is recreated
juliusmarminge 7e369b6
Merge remote-tracking branch 'origin/main' into fix/issue-24390
juliusmarminge ed798dd
Merge remote-tracking branch 'origin/main' into fix/issue-24390
juliusmarminge f40a41a
fix(server): only leftover directories count as an abandoned worktree
juliusmarminge 8a9d132
Merge remote-tracking branch 'origin/main' into fix/issue-24390
juliusmarminge 7d0ef87
Merge remote-tracking branch 'origin/main' into fix/issue-24390
juliusmarminge 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
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.
Recursive removal can delete files in a junction target.
The leftover check accepts a
node_modulesor.nextentry whenfileSystem.statreports a directory (line 60).statfollows links, so a junction passes. Line 153 then callsfileSystem.remove(worktreePath, { recursive: true }).With Node.js 22.16.0, which the declared engine range allows, the recursive removal can enter a locked junction and delete files in its target:
rmdiron the worktree root returnsENOTEMPTY. The removal then calls_rmchildren.lstatreports a symbolic link. The removal callsunlink. IfunlinkreturnsEPERMon Windows, the removal callsfixWinEPERM.fixWinEPERMcallsstat, which follows the junction and reports a directory. It then calls_rmdir.rmdirreturnsEPERM, the removal treatsEPERMas "not empty" and calls_rmchildrenon the junction. That call reads the target and removes its children.This removal can delete files outside the leftover worktree. The fix in nodejs/node#63709 targets main. Confirm which supported Node.js lines include it before relying on the behavior being absent.
Do not classify entries with
stat. Check each leftover entry for a link before any recursive removal. Fail the recovery when a link is present. Alternatively, remove each link entry without recursing into its target.Source: Learnings