-
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
3.3.1 - cypress often fails to load in open mode - websocket error #4366
Comments
maybe this is the same as this? #4359 (comment) If so... I've tried with or without the base url and same error.
I only use the above env variables to stop cypress having an annoying reload every time you open a spec. |
@lukeapage Can you share the full |
I've asked my colleague to send details to support@cypress when he's back from vacation |
Okay, sounds good. If anyone else reading this is experiencing this, please share your DEBUG logs to shed some light on the issue. |
@lukeapage Can you to try Cypress 3.3.2? We made some bugfixes to websockets along with other network improvements and it might fix this issue. No |
I got the same error not sometimes but always when working with v3.2.0 and above, I downgraded to 3.1.5 and it's working now. |
@shaharkazaz No idea yet. Since you can reliably get this to happen, can you share the full debug logs from when you run Cypress and experience this issue? It would help a lot to debug the cause of this and get it fixed. |
@shaharkazaz Any updates on sending the debug logs? |
@flotwig @jennifer-shehane Hey, sorry I wasn't available in the last couple of days, I'll get the logs today |
@jennifer-shehane @flotwig
|
@shaharkazaz Thanks for providing this! You do not have a Also, did you test this with 3.4.0 or another version? If both of those answers are "yes", can you share the complete debug logs from the session? There's some startup info that is useful to have in there too. |
@flotwig Happy to help 🙂 Is there a way for the logs to be written to a file? there is too much output in these logs |
For sure, you can use shell redirection:
|
Ya I figured using shell redirection would probably be the answer 😁 |
@flotwig did the logs help? any idea what's going on? |
I have the same issue. Tried 3.1.5 and 3.4.0 on mac with Chrome and Electron. |
Hmm, I am curious if the issue is related to launching Cypress for a project listening on port 80. @fernando-paredes or @shaharkazaz Could you try running your server on a non-standard port? Launch your project on port 3000 for example, then run Cypress with |
@flotwig my server is running on port 4200 |
Oh, I see that now. :P I did notice that the other two users in the thread are using port 80, so hopefully they can test it out and we can see if it's related to their issue. Potentially related (same error): #4763 |
Finally, it worked for me after "plugins->index.js" file is updated with the following arguments
|
Closing as resolved. Please open a new issue with a reproducible example if you are encountering an issue similar to the one described in this thread. |
@vijesh-koroth -- how do we use this in the index.js in plugins?Is this correct. not working for me args.push('--disable-gpu') |
Current behavior:
Desired behavior:
No error
Steps to reproduce: (app code and test code)
This happens intermittently but very often on 3.3.1. If you log off and on again it is fine.
If you switch back to cypress 3.3.0, even without logging off it is fine.
Versions
3.3.1 (3.3.0 is fine)
OS: windows
Most of us use proxies, usually fiddler. When 3.3.0 was release we had to have this:
One of our devs reckons the following proxy settings in 3.3.1 fix this bug:
I believe the NO_PROXY needing "undefined" was due to another bug you had in your network code.
The text was updated successfully, but these errors were encountered: