Retry dispatch-ticket connection establishment failures - #177
Merged
Merged
Conversation
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
1 participant
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.
Closes #176.\n\nRetries only errors classified by reqwest as connection-establishment failures. The budget is three attempts with bounded 100/200 ms delays. HTTP errors, response/read timeouts, ticket verification, eligibility, and ranking semantics are unchanged.\n\nLocal verification:\n-
cargo test directory_connect_retry_tests --locked\n-cargo fmt --check\n-git diff --check\n-cargo clippy --lib --locked -- -D warningsreaches the crate and reports three pre-existing dead-code findings outside this patch (restricted_directory_context,submit_to_node_ids, and restricted-directory profile constants). No new Clippy finding was introduced.