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(cli): Map error kind to PermissionDenied when symlinking fails due to permissions #25398

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

nathanwhit
Copy link
Member

Fixes #25333.

We fall back to junctions if the error kind is PermissionDenied but the std library actually sets the kind to Uncategorized if the symlink fails due to insufficient privileges. This was causing the fallback to not actually fall back in this case.

@dsherret dsherret added the backport:1.46 This PR needs to be backported to v1.46 branch label Sep 3, 2024
Copy link
Member

@dsherret dsherret left a comment

Choose a reason for hiding this comment

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

LGTM!

@nathanwhit nathanwhit merged commit 105c571 into denoland:main Sep 3, 2024
17 checks passed
@nathanwhit nathanwhit deleted the windows-symlinks branch September 3, 2024 21:42
lucacasonato pushed a commit that referenced this pull request Sep 4, 2024
…due to permissions (#25398)

Fixes #25333.

We fall back to junctions if the error kind is `PermissionDenied` but
the std library actually sets the kind to `Uncategorized` if the symlink
fails due to insufficient privileges. This was causing the fallback to
not actually fall back in this case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:1.46 This PR needs to be backported to v1.46 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Scripts that use npm packages do not work with Deno v1.46.2 on Windows
2 participants