-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
illegal operation on a directory #800
Comments
Interesting bug. Is this a single project with this problem or does every project have the same access problem? How did you install Cypress - |
Yes I tried on two computers encountered same exact issue on both computers.
As per the instructions, opened cypress server I can see sample tests then I added just one sample first test .
Tried running it I see error, can’t progress much .
Cypress Installed at project root directory : npm install cypress -save-dev
Cypress is in the package.json
…Sent from my iPhone
On 25 Oct 2017, at 1:57 am, Gleb Bahmutov ***@***.***> wrote:
Interesting bug. Is this a single project with this problem or does every project have the same access problem? How did you install Cypress - npm i -D cypress from the project folder /Users/potlar/cy-poc?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
GET /__cypress/runner/fonts/fontawesome-webfont.woff2?v=4.7.0 304 0.906 ms - -
Error: EISDIR: illegal operation on a directory, open '/Users/potlar/Library/Application Support/Cypress/cy/production/projects/cypress-073855131d8053ebc1daebbb0464b31a/bundles/cypress/integration'
- Error
GET /__cypress/iframes/ 200 23.354 ms - 665
Error: Cannot find module '/Users/potlar/ANZ/sola/csp-angular-ui-sola/e2e/cypress/cypress/integration' from '/Users/potlar/ANZ/sola/csp-angular-ui-sola/e2e/cypress'
- async.js:55
[cypress]/[server]/[browser-resolve]/[resolve]/lib/async.js:55:21
- async.js:69 load
[cypress]/[server]/[browser-resolve]/[resolve]/lib/async.js:69:43
- async.js:92 onex
[cypress]/[server]/[browser-resolve]/[resolve]/lib/async.js:92:31
- async.js:22
[cypress]/[server]/[browser-resolve]/[resolve]/lib/async.js:22:47
- polyfills.js:284
[cypress]/[server]/[graceful-fs]/polyfills.js:284:29
Error: EISDIR: illegal operation on a directory, open '/Users/potlar/Library/Application Support/Cypress/cy/production/projects/cypress-073855131d8053ebc1daebbb0464b31a/bundles'
- Error
GET /__cypress/tests?p=cypress/support/index.js-512 200 8.466 ms - -
{ Error: EISDIR: illegal operation on a directory, read
at Error (native)
errno: -21, code: 'EISDIR', syscall: 'read' }
Error: EISDIR: illegal operation on a directory, read
at Error (native)
GET /__cypress/tests?p=-460 - - ms - - |
Very weird, and the disk is not out of space? We have never seen this error when running Cypress on Macs |
I discovered the reason why I’m getting this error.
My app built using angular 1.5 framework so cypress somehow throwing this error when try to open app
…Sent from my iPhone
On 29 Nov 2017, at 9:14 am, Gleb Bahmutov ***@***.***> wrote:
Very weird, and the disk is not out of space? We have never seen this error when running Cypress on Macs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I have very rarely and occasionally seen this error but I couldn't ever figure out the underlying cause. It might be having to do with the application you're visiting. Can you try running something like the Kitchen Sink? You did not specify if this is happening on all applications or just yours. You said "you added one sample test". Does this mean that it crashes only when you save a file? Can you be more descriptive of the exact steps you perform to cause this to happen? Perhaps taking screenshots or sending us the recorded video. Something I thought of would be a permission issue related to Also have you tried upgrading to newer Cypress versions? We've done a lot of work in the spec code handling. |
I think what is actually happening is that your app is implementing a security mechanism that is redirecting Cypress to an invalid URL, and when it attempts to serve this file it instantly crashes because it's not valid and we can't read it. I think that is the only times I've seen this error. |
I'm going to close this until more information is provided, or assuming its security related there are already many open issues talking about how to work around this. |
I got this error when my SPA UI framework (Ember.js) was configured to use the hash in the url. cy.visit('http://localhost:4200');
//once loaded is forwarded to localhost:4200/#/dashboard When I changed my application's router to use the "history" strategy, I no longer received this error. cy.visit('http://localhost:4200');
// once loaded is forwarded to localhost:4200/dashboard |
Bug:
Is this a Feature or Bug?
I opened cypress using
cypress open
Server starts and shows me the newly created spec file
I ran the spec file
It opens a browser with running and immediately I see the following errors;
The text was updated successfully, but these errors were encountered: