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
Read only FS throwing EPERM instead of EACCESS #16933
Comments
5 tasks
cypress-bot
bot
added
stage: work in progress
stage: needs review
The PR code is done & tested, needs review
and removed
stage: work in progress
stage: needs review
The PR code is done & tested, needs review
labels
Jun 14, 2021
cypress-bot
bot
added
stage: needs review
The PR code is done & tested, needs review
and removed
stage: waiting
labels
Jun 22, 2021
The code for this is done in cypress-io/cypress#16934, but has yet to be released. |
cypress-bot
bot
removed
the
stage: needs review
The PR code is done & tested, needs review
label
Jun 22, 2021
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current behavior
Running with Bazel in a read only FS it throws an EPERM error on MacOS 11.2.3 (not sure about others). Same as #1281 just different error code (EPERM instead of EACCES).
Desired behavior
Print a warning like with EACCES here: https://github.com/cypress-io/cypress/blob/develop/packages/server/lib/util/settings.js#L128-L130
Test code to reproduce
It is a whole Bazel setup and the issue is straightforward but if needed I can put something up.
Versions
The text was updated successfully, but these errors were encountered: