feat: periodic recovery after WS failure#225
Merged
Merged
Conversation
evchip
reviewed
Jan 5, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
After WebSocket hangs up, tries to reconnect and process missed blocks every 5 seconds. This replaces processing of missed blocks which was triggered in
onLogsbinding - and required waiting for next intent do be opened.Motivation and Context
Needed for missed intents to be processed ASAP after WebSocket reconnects. That prevents them from hitting their
fillDeadlineand also improves UX.How Has This Been Tested?
Tested on a local instance of
sealed-bid-auctionwithsolverBot.ts, against mainnetv09contracts.Types of changes (remove all unchecked types)
Checklist: