Skip to content
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

fix(ext/node): map ERROR_INVALID_NAME to ENOENT on windows #26475

Merged
merged 1 commit into from
Oct 23, 2024

Conversation

kt3k
Copy link
Member

@kt3k kt3k commented Oct 22, 2024

In libuv on windows, ERROR_INVALID_NAME is mapped to ENOENT, but it is mapped to EINVAL in our compat implementation, which causes the issue #24899.

ref: https://github.com/libuv/libuv/blob/d4ab6fbba4669935a6bc23645372dfe4ac29ab39/src/win/error.c#L138

This PR fixes the above.

closes #24899
closes #26411
closes #23635
closes #21165
closes #19067

Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for tracking this down!

@kt3k kt3k merged commit 285635d into denoland:main Oct 23, 2024
17 checks passed
@kt3k kt3k deleted the fix-error-invalid-name-mapping branch October 23, 2024 02:28
bartlomieju pushed a commit that referenced this pull request Oct 25, 2024
In libuv on windows, `ERROR_INVALID_NAME` is mapped to `ENOENT`, but it
is mapped to `EINVAL` in our compat implementation, which causes the
issue #24899.

ref:
https://github.com/libuv/libuv/blob/d4ab6fbba4669935a6bc23645372dfe4ac29ab39/src/win/error.c#L138

closes #24899 
closes #26411
closes #23635
closes #21165
closes #19067
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment