-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
fs: fix fs.rm
support for loop symlinks
#45439
Conversation
The tests have quite a bit of duplicated code (both existing and my new tests). I can add a new block at the bottom of the file that adds the new tests for the sync, async and promise version without so much duplicated code if you want. |
This comment was marked as outdated.
This comment was marked as outdated.
For tests only, I generally prefer the repetition. (Ref: https://stackoverflow.com/a/11837973/436641) |
fs.rm
support for loop symlinks
132ecfc
to
8455a62
Compare
Thanks for fixing the commit message, one question though: For something like addressing the review comments, should I always amend and force push or is another commit okay for this (I guess you can always squash at the end)? Also I think the title of the PR is no longer 100% accurate, because deleting invalid links was also broken before (the
The loop thing was just the first issue I encountered. |
should I always amend and force push or is another commit okay for this (I guess you can always squash at the end)?
Pushing more commits is the recommended way, it's a much better experience for folks reviewing the PR as otherwise GitHub is not able to show what's changed since the last review. When landing the PR, we can ask the commit-queue to squash all the commits into the first one, so as long as its commit message is accurate, no need to force push. The other reason to force push would be if you needed to rebase on top of `main`, e.g. to fix a git conflict (merge commits tend to break our tooling).
… On 13 Nov 2022, at 09:04, Nathanael Ruf ***@***.***> wrote:
Thanks for fixing the commit message, one question though: For something like addressing the review comments, should I always amend and force push or is another commit okay for this (I guess you can always squash at the end)?
Also I think the title of the PR is not longer 100% accurate, because deleting invalid links was also broken before (the stat call failed with ENOENT):
nathanael ~/tmp λ tree
.
└── b -> a
nathanael ~/tmp λ node -e 'fs.rmSync("b")'
node:internal/fs/utils:344
throw err;
^
Error: ENOENT: no such file or directory, stat 'b'
at Object.statSync (node:fs:1538:3)
at __node_internal_ (node:internal/fs/utils:793:8)
at Object.rmSync (node:fs:1213:13)
at [eval]:1:4
at Script.runInThisContext (node:vm:129:12)
at Object.runInThisContext (node:vm:305:38)
at node:internal/process/execution:76:19
at [eval]-wrapper:6:22
at evalScript (node:internal/process/execution:75:60)
at node:internal/main/eval_string:27:3 {
errno: -2,
syscall: 'stat',
code: 'ENOENT',
path: 'b'
}
The loop thing was just the first issue I encountered.
—
Reply to this email directly, view it on GitHub <#45439 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADNFTDN6WSRGOPCR5JPUCXDWICOKVANCNFSM6AAAAAAR6O64FQ>.
You are receiving this because you commented.
|
/cc @nodejs/fs |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
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.
LGTM with a suggestion.
Looks like |
Co-authored-by: Livia Medeiros <livia@cirno.name>
I think this is intended. In general, symlinks are supposed to be transparent, so accessing invalid symlink should be equal to accessing its destination (e.g. nonexistent file). Testing if broken symlink still exists can be performed explicitly with |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Landed in 6f9175d |
Thanks for the contribution! |
Fixes: nodejs#45404 PR-URL: nodejs#45439 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Minwoo Jung <nodecorelab@gmail.com>
Fixes: #45404