Utilize gRPC response item timeout for all stream items instead of only version tracking #165
Conversation
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
…ly version tracking
jtang17
approved these changes
Jan 29, 2026
| Some(Ok(r)) => { | ||
| self.reconnection_retries = 0; | ||
|
|
||
| // The processed range may not exist if using the v1 transaction stream. |
Contributor
Author
There was a problem hiding this comment.
Not really but I think it's ok to keep just to be safe
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.
In production environments, the stream is forced to restart after 5 minutes due to API Gateway behavior. This is not the case when connecting to streams that do not go through API Gateway (i.e. localnet). In some cases, the stream will remain open but stuck. This change will utilize the timeout in config to restart the stream if transactions have not been received for that long. Previously the timeout was only used when waiting for the version tracking request.