-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: replace reconnecting-jsonrpsee-ws-client
with subxt-reconnecting-rpc-client
#1705
Merged
Merged
Changes from 1 commit
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
f3dcdd0
feat: add native subxt rpc reconn client
niklasad1 d0d8be0
Merge remote-tracking branch 'origin/master' into add-dedicated-subxt…
niklasad1 901ce74
add jsonrpsee dep to reconnecting-client
niklasad1 63eefcc
Update subxt/src/backend/rpc/reconnecting_rpc_client/tests.rs
niklasad1 01b5319
fix grumbles
niklasad1 3f69b64
Merge remote-tracking branch 'origin/add-dedicated-subxt-rpc-reconn-c…
niklasad1 7aef278
add simple wasm test for reconnecting client
niklasad1 9f18d59
fix test build
niklasad1 d942471
cargo fmt
niklasad1 f0d8282
remove reconnect apis
niklasad1 8244dd7
Merge branch 'master' into add-dedicated-subxt-rpc-reconn-client
niklasad1 b40819a
Merge branch 'master' into add-dedicated-subxt-rpc-reconn-client
niklasad1 fe6e62d
Update testing/wasm-rpc-tests/tests/wasm.rs
niklasad1 7f271ca
Update subxt/src/backend/rpc/reconnecting_rpc_client/tests.rs
niklasad1 37727c0
Update subxt/src/backend/rpc/reconnecting_rpc_client/tests.rs
niklasad1 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
This file contains 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
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clean up tokio, perhaps we can replace it with futures channels and stuff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll prob want a tokio feature flag or similar anyway so that we can make it easy to start up the
UnstableBackend
etc!I see
web
enabledtokio?/sync; would
weband
tokio/sync` work together though?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, tokio/sync works for wasm/web but that could easily be replaced by futures channel
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I forgot that I used
tokio::sync::Notify
so I prefer to keep tokio but not runtime agnostic but it's doesn't matter anyway because jsonrpsee is already using tokio channels.We could change that though if becomes an issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup I don't mind that it uses tokio since jsonrpsee does anyway, so we don't really gain anything by trying to remove it anyways from this I guess!