Skip to content
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

feat: fatal exit upon loss of connection to sequencer #24

Merged
merged 1 commit into from
Dec 3, 2024

Conversation

anomit
Copy link
Member

@anomit anomit commented Dec 3, 2024

This is a hotfix that ensures the local collector exits cleanly and is brought back up by a docker compose restart policy of the snapshotter node with which it is bundled.

Checklist

  • My branch is up-to-date with upstream/main branch.
  • Everything works and tested for major version of Python/NodeJS/Go and above.
  • I ran pre-commit checks against my changes.
  • I've written tests against my changes and all the current present tests are passing.

Current behaviour

Currently the local collector has difficulty establishing a single TCP connection to the sequencer during times of network congestion, which causes further issues with multiplexing libp2p streams on to it.

New expected behaviour

As described in first section of issue description.

Change logs

Changed

  • exit on loss of connection to sequencer

Deployment Instructions

NA

@anomit anomit self-assigned this Dec 3, 2024
@anomit anomit merged commit 5cbdac2 into main Dec 3, 2024
2 checks passed
@anomit anomit deleted the chore/fatal-exit-conn-lost branch February 10, 2025 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants