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

problem: treats a fresh Syncing node as a normal one #274

Merged
merged 1 commit into from
Nov 21, 2023

Conversation

splix
Copy link
Member

@splix splix commented Nov 21, 2023

solution: additional checks and switch to SYNCING state if lag is too large
fix: #259

solution: additional checks and switch to SYNCING state if lag is too large
fix: #259
@splix splix merged commit 25829ba into master Nov 21, 2023
3 checks passed
@splix splix deleted the fix/large-lag-no-syncing branch November 21, 2023 02:53
splix pushed a commit that referenced this pull request Nov 27, 2024
…ities (#274)

Helps us to distinguish which multistreams can be used for subscriptions
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.

Dshackle doesn't detect lag if geth is at 0 height but isn't syncing
1 participant