Refactor timeout #179
Open
Refactor timeout #179
+21
−48
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
Rahamath-unnisa
force-pushed
the
refactor-timeout
branch
from
667496a to
0c5ae27
Compare
|
Hi !I’ve re-signed all commits.The CI is pending maintainer approval — please let me know if any further changes are needed. |
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.
Fixes #151
This PR updates the ElectrumClientBuilder (and related builder logic) to use std::time::Duration for timeout configuration, instead of a u8 value representing seconds.
Notes to the reviewers
Replaced timeout: Option with timeout: Option in the builder.
Adjusted all relevant function calls and tests accordingly.
Confirmed that all existing integration tests pass.
Checklists:
I've signed all my commits
I followed the contribution guidelines
I ran cargo fmt, cargo clippy, and cargo test before pushing
I’m linking the issue being fixed by this PR
Supersedes #178
This replaces the previous PR which had CI and branch issues.