Draft
Conversation
From a case seen on testnet where the host-listener was stuck by alloy looping on bad node message. The timeout will cut that loop and force host-listener to retry and reconnect.
rudy-6-4
changed the base branch from
main
to
rudy/fix/host-listener/break-alloy-hidden-infinite-loop-on-bad-message
rudy-6-4
force-pushed
the
rudy/fix/host-listener/break-alloy-hidden-infinite-loop-on-bad-message
branch
6 times, most recently
from
4a5848c to
2fe4586
Compare
rudy-6-4
force-pushed
the
rudy/fix/host-listener/break-alloy-hidden-infinite-loop-on-bad-message
branch
from
2fe4586 to
1654b94
Compare
Base automatically changed from
rudy/fix/host-listener/break-alloy-hidden-infinite-loop-on-bad-message
to
main
January 30, 2026 11:34
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
1 participant
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.
No description provided.