Investigate proxy execution environments failing to start #2372
Assignees
Comments
Mrtenz
pushed a commit
that referenced
this issue
May 3, 2024
Fixes a problem with proxy execution environments having unintentionally low timeout values. The assumption is that `initJob` resolves once the execution environment is perceived to be ready for requests and therefore we ping the execution env with a very low timeout to detect issues and fail early. However, `initJob` was resolving way before the actual proxy executor was ready. This problem can be fixed by effectively pinging the execution environment as part of the initialization process of proxy executors as this loads the proxy executor and doesn't resolve until the executor responds. Fixes #2372
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Investigate proxy execution environments failing to start, specifically in the MV3 environment.
May be related to slow internet connection and a race condition in setting up proxy executors.
The text was updated successfully, but these errors were encountered: