-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
No traceback for: EACCES: permission denied, unlink #6058
Comments
Is there any progress here? I have a virtual machine with Ubuntu Server (Linux), but the files come from a shared folder of a Windows OS. Possible? |
@CreativeNative The Error might be due to Linux's File System Permission issue. Please try to use the command with |
Thanks for your response. It's indeed a problem with the Linux file system permissions. I use this option now, and it works for me.
|
@CreativeNative Then you should close this issue! |
@Rajdeep-TG I didn't create the issue, so I can't close it. -_- |
@domenkozar It seems that you're using Linux or macOS (as per the file includes |
Not much to go off here so I'll close this |
Running random commands as root just to fix permission issue is not really acceptable. It only takes one bad script to mess up your system. This issue is about the fact that the error message does not really provide any hints as to what could be causing the permission issue in the first place. |
@jtojnar The error message shows
|
What I wonder about is why the file is being deleted in the first place. Looking at the source code, it should actually points us to a
But unfortunately, the “trace” in the yarn-error.log offers no more context:
So this issue is really about improving the debugging information by providing full stack trace in the error message. Edit: Searching for |
Yarn throw an error without a trace, making it really hard to know where it's coming from.
The text was updated successfully, but these errors were encountered: