-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Cypress open hangs for a minute or two before loading #29171
Comments
Hello,
|
@AlexandreRozier Thanks for the investigation. That sixty seconds is suspicious. This was introduced in 10.0, so it's interesting that @AlexGuironnetRTE mentions this behavior showing up in an older version. I wonder if it's a combination of something recent with this code. |
Thanks for the reply. Turns out my issue with 13.2.0 was the same as #27813. Clearing the cache and reinstalling as suggested made the error go away. And then.... cypress open hangs. So that means whatever might interact with the function from 10.0 as you said would have been introduced with 13.2.0... |
I also tried from home to rule out any company proxy timeout or anything of this kind, and I have the same behaviour. |
Thks for the reply ! I don't think
|
@jennifer-shehane I'm adding a bug repro to this issue , hopefully this will help ! Steps :
|
We are facing the same issue with Cypress 13+. Cypress 12.17.4 launches quickly. Cypress starts hanging for us at 13.0.0 on the loading screen. At least we are getting the "loading animation" instantly 😉. We have tested 13.0.0, 13.1.0, 13.2.0 and 13.7.2. All are hanging for several minutes. Our system setup: In the logs I can see a lot of timeouts after 4 minutes appearing right at the moment where the "Welcome to Cypress" page appears. Debug log
|
@AlexandreRozier I'm not able to run this repo, it errors without access to https://devin-depot.rte-france.com/ Could you update it? |
Due to issues reported to my Cypress plugin cypress-ntlm-auth, I looked into slow/hanging startups. These are my findings: When started with Looking into the source, I found that the above requests are not performed on Figuring out why the issue appears behind a corporate proxy took quite some digging... Why does the host header become incorrect?Cypress uses the package
After this, the How can it be fixedThe simple solution of passing along either port or defaultPort in the options to the fetch call does not work.
Which solution seems most suitable? Option 3 would only require a limited effort, but I cannot determine if this could cause issues in other calls to fetch. I would be happy to help out, but option 2 requires someone highly familiar with the different use cases of the agent. There are likely many other issues reported that are related to this issue. For instance communication with the cypress cloud services may be affected. Hence I think there is great value to resolve this. |
Hey @bjowes, thanks for sharing your detailed investigation. I'll see if the team can look at this. In the meantime we're always welcome to accept PRs for fixes. |
Great! As stated, I’ll be happy to help but please check with the team
which option makes most sense to them before I start working on it.
tors 25 apr. 2024 kl. 20:47 skrev Jennifer Shehane ***@***.***
…:
Hey @bjowes <https://github.com/bjowes>, thanks for sharing your detailed
investigation. I'll see if the team can look at this. In the meantime we're
always welcome to accept PRs for fixes.
—
Reply to this email directly, view it on GitHub
<#29171 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABCHR3EEQBFKOESDEETF2YDY7FFS7AVCNFSM6AAAAABE7ICUKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZXHE2TCMJZGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@bjowes Thanks so much for the detailed investigation! We already use Refactoring to the more standard pattern is probably the more sustainable approach. We would be fine with either of these, though I have a slight preference towards the latter :) |
Thanks bjowes for your input ! I can confirm we're also having the same issue : cypress open is fast when we're working at home, but slow when we're on-site. So it seems we're having the same problem :) @jennifer-shehane I'm adding a simpler repro archive below; I recreated one from your |
Ok @cacieprins - PR prepared. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior
Hi !
For some time now, cypress open takes a couple minutes to start when running
npx cypress open
Here are the steps we've encountered:
1.Cypress browser window is blank
Desired behavior
npx cypress open
opens cypress window quicklyTest code to reproduce
bug-repro.zip
I dumped the output of
DEBUG=* npx cypress open --config-file cypress/cypress.local.config.ts --browser edge
in this file :out.log
It seems that the app stops being stuck shortly after the following logs appear :
The "execution time" associated with the command
cypress:data-context:sources:GitDataSource Refreshing git data
was of 1minute (pretty long), so I dug a bit in cypress source code (GitDataSource.ts
) , but it seems that the "1min" delay is due to this part :Note that we don't have any delay with
cypress run
, and this piece of code is ran only in open mode, that's why I thought this was relevant !By downgrading to cypress 12.5.0, this issue disappears and cypress start normally. Here are the logs of a successful execution :
working.log
Interestingly, these logs do not contain the lines that appear when cypress stops being stuck (see above), so they must be unrelated to the issue....
And finally, cypress version 13.4.0 also has this issue (the only other I tried so far)
Sorry for the lack of other clues, I hope you'll have the time to take a look ! And thanks again for Cypress, we're using it everyday :)
Cypress Version
13.6.4
Node version
v16.15.0
Operating System
Ubuntu 20.04.5 LTS Release
Debug Logs
Other
No response
The text was updated successfully, but these errors were encountered: