Reduce CLI client timeout to 30 seconds#491
Merged
mozzieongit merged 1 commit intomainfrom Mar 3, 2026
Merged
Conversation
bal-e
approved these changes
Mar 3, 2026
Contributor
bal-e
left a comment
bal-e
left a comment
There was a problem hiding this comment.
I don't have any problems with this change.
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
2 participants
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.
Currently, the CLI client timeout is set to 2 minutes. That is a really long time to wait for a TCP connection timeout or other timeouts.
Are our HTTP endpoints fast or do we block on some long running processes still?
I remember that earlier zone loading would block the CLI and wait for as long as the zone needs loading, and now it reports back quickly that the zone has been added.