-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
win: use long directory name for handle->dirw #1769
Conversation
I see, it doesn't work because watching is recursive. We'll have to go with the other solution. |
`uv_relative_path` assumes `dir` is a prefix of `filename`, which is not the case when `handle->dirw` is a short path. Fixes: nodejs/node#19170
Let's try again: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/750/ |
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.
CI is green, change LGTM
Would it be possible adding a test for this? |
nodejs/node#19170 is reproducible only with user names longer than 8 characters, not sure how one could test such scenario. |
I don't know either 🤷♂️ . @bzoz do you think it can be possible? |
Sure: use https://github.com/libuv/libuv/blob/v1.x/test/test-fs-event.c, add one more test case with The username is just a coincident, the original issue reproduces with any long directory name watched through its short name. Besides |
Added a test. |
The failures seem unrelated. |
`uv_relative_path` assumes `dir` is a prefix of `filename`, which is not the case when `handle->dirw` is a short path. Refs: nodejs/node#19170 PR-URL: #1769 Reviewed-By: Bartosz Sosnowski <bartosz@janeasystems.com>
Landed in 7e865b6 |
uv_relative_path
assumesdir
is a prefix offilename
, which is notthe case when
handle->dirw
is a short path.Fixes: nodejs/node#19170