Repository navigation
Conversation
… wake and a waking command On hosted, the internal service's first boot of a sandbox ran past the thirty seconds the remote backend gave every request, so every create failed at the proxy while the service was still at it.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
On hosted, the internal service's boot of a sandbox runs past the thirty seconds the remote backend gave every request: a boot on a small instance, the first after a start with the software to fetch, takes a minute or two. Create and wake get three minutes, and a command gets that on top of its own timeout, since it may wake the sandbox it runs in first. Sleep and destroy keep thirty seconds. The internal service's own bound on a boot is three minutes as well (personalagentproxy/internal#43).
Open workspace in Conductor