-
Notifications
You must be signed in to change notification settings - Fork 209
Reclaim request id for unsubscribe requests #274
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
Conversation
niklasad1
left a comment
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.
Thanks, nice catch
However, when #269 when/if merged this logic will be simplified
…ech/jsonrpsee into return-request-id-on-unsubscribe
Hmm, really? Please open issue |
|
Yeah - I'm getting this when trying to run UPD: actually removing |
| } | ||
|
|
||
| #[tokio::test] | ||
| #[ignore] |
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.
What is this about, are these tests failing even with this fix?
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.
the nodes have been down so ignored those for now ^
When unsubscribe request is sent, the
send_backisNone(see here). When response to this request is received, the request id is not reclaimed by the request manager (see this and this) => if app starts and drops subscriptions, it'll end up with MaxSlotsExceeded error. Like it already happened in paritytech/parity-bridges-common#909 .Unfortunately, I'm unable to compile master branch of
jsonrpseewith latest stable rust => can't run tests and see if this patch breaks something. But at least applying this patch to the alpha.4 solves our issue.