Repository navigation
fix: escalate --ladder on timeouts - #78
Merged
Merged
Conversation
paulius-krutkis-dcd
approved these changes
Oct 26, 2026
ASDCD154
force-pushed
the
ladder-escalate-timeout
branch
from
October 27, 2026 12:56
52f5cb4 to
f5b2c57
Compare
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.
Timeouts never moved up the ladder, so a site that times out direct requests (Best Buy) failed without trying the next tier.
timeoutnow escalates, and socket-level timeouts (read: operation timed out) are classified astimeoutinstead ofnetwork. The wizard's higher-tier tip covers timeouts too. The Best Buy repro now reachesprovider.