-
Notifications
You must be signed in to change notification settings - Fork 683
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
Bridges - changes for Bridges V2 - relay client part #4494
Conversation
1cdb84f
to
7a394d8
Compare
@svyatonik In traitified v2 client we are using shared subscriptions, so #4481 shouldn't be a problem when we talk about long-lived subscriptions (justification). But we need to test it for transaction subscriptions - right now I've rebased completely without #4481 |
c4c55e2
to
12c59b5
Compare
* Revert "Revert new client (#2153)" This reverts commit 17cf7b596170419a1e9b9d39d7e329acdb1a87de. * add comment re cache to CachingClient (#2162) * do not wait for reader when sending items (#2163) * Use unsync cache + async-aware sync primitives (#2164) * use unsync cache + async-aware sync primitives * clippy * trigger CI * Revert "trigger CI" This reverts commit b5c1405492409b85abf552ba0b089c000824f722.
…ble (#2206) * Avoid using extra background task for TransactionTracker * Add docs
* final check before transaction submit * pass pre-encoded transaction to validate
* read best + best finalized headers from subscription * spelling * clippy
12c59b5
to
6a021c8
Compare
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.
FWIW: all code changes were already reviewed before in a https://github.com/paritytech/parity-bridges-common/ repository. I did a shallow check and porting looks good and should work with all existing bridges. However I also want to perform that check: #4494 (comment). Will do that tomorrow and approve if all is ok or push some commits to fix it if changes are required
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.
Checked the possible subscription leak issue - all is good
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.
Did shallow review only since this has already been reviewed on development branch
Cherry-picked fix from upcoming paritytech#4494 --------- Co-authored-by: Svyatoslav Nikolsky <svyatonik@gmail.com> Co-authored-by: command-bot <>
…mplemented for T: Client<C>
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.
Also took just a high-level look since this has already been reviewed before. Looks good !
* Dienerized to polkadot-sdk@bko-bridges-backports-and-nits * cargo update -p sp-io * Change substrate-relay version * Update polkadot-sdk master ref * Setup latest master with merged: paritytech/polkadot-sdk#4494 * Change relayer version for release --------- Co-authored-by: Svyatoslav Nikolsky <svyatonik@gmail.com>
Cherry-picked fix from upcoming paritytech#4494 --------- Co-authored-by: Svyatoslav Nikolsky <svyatonik@gmail.com> Co-authored-by: command-bot <>
Contains mainly changes/nits/refactors related to the relayer code (`client-substrate` and `lib-substrate-relay`) migrated from the Bridges V2 [branch](paritytech#4427). Relates to: paritytech/parity-bridges-common#2976 Companion: paritytech/parity-bridges-common#2988 ## TODO - [x] fix comments ## Questions - [x] Do we need more testing for client V2 stuff? If so, how/what is the ultimate test? @svyatonik - [x] check [comment](paritytech#4494 (comment)) for more testing --------- Co-authored-by: Svyatoslav Nikolsky <svyatonik@gmail.com> Co-authored-by: Serban Iorga <serban@parity.io>
Contains mainly changes/nits/refactors related to the relayer code (
client-substrate
andlib-substrate-relay
) migrated from the Bridges V2 branch.Relates to: paritytech/parity-bridges-common#2976
Companion: paritytech/parity-bridges-common#2988
TODO
Questions