-
Notifications
You must be signed in to change notification settings - Fork 6
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
fix: use batch subscribe and remove 4050 #388
Conversation
54f0342
to
4abd2ba
Compare
metrics.relay_batch_subscribe_request(start); | ||
} | ||
// TODO process each error individually | ||
// TODO retry relay internal failures? |
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.
src/publish_relay_message.rs
Outdated
Error::Response(rpc::Error::Handler( | ||
SubscriptionError::SubscriberLimitExceeded, | ||
)) => { | ||
// FIXME figure out how to handle this properly; being unable to subscribe means a broken state |
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.
Consider creating an issue to address this and linking it here.
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.
This issue was root caused and no issue should currently exist because Notify Server always subscribes first. Confirmed with logs.
Removing this error handling logic in 6e4cb5c as the error should not happen.
Description
Use more lightweight renewal process now that IRN has shipped. Details here. Instead of needing to extend the TTL of the topic subscription with 4050 messages, the topic subscription is 30 days by default.
Remaining work:
Blocked by https://github.com/WalletConnect/rs-relay/issues/1457Update to SDK version aboveHow Has This Been Tested?
Not tested
Due Diligence