Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Additional details
Prior to sending the API request to create a run, Cypress attempts to determine how best to make requests to the Cypress Cloud via a "preflight" request. This request is first made without the
CombinedAgent
that supports HTTP/S proxies, to one API domain. If this request fails, the second request is made to a different API domain, and uses theCombinedAgent
that uses proxy information in theHTTP_PROXY
/HTTPS_PROXY
environment variable.This is done to accommodate a wide variety of network configurations.
For network configurations that block non-proxied requests to the Cypress Cloud API, the request to create a run will always carry a 60 second overhead. However, this initial request is important to determine the network capabilities of the machine that is running the tests.
With this PR, the
CYPRESS_INTERNAL_INITIAL_PREFLIGHT_TIMEOUT
environment variable can be set. This can be reduced below the default 60 seconds to trim the overhead. This environment variable can also be set to -1, which will disable the non-proxied preflight request.Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?