shutter: recover from unwinds before the first keyper set activates
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 53/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- go
- Domain
- backend, distributed-systems
Research direction
Start with KsmEonTracker.readEonAtNewBlockEvent and trace how its cached currentEon and GetKeyperSetIndexByBlock behave when the chain unwinds before the first keyper set activates. Add regression coverage for the reported block 4 → 10 → 9 unwind and recovery after activation becomes canonical again. Confirm the new handling recovers from a missing active set while preserving errors from unrelated contract failures.
Written by the indexing model from the issue text.
Description
A reorg can stop Shutter after the keyper-set manager has been deployed but before its first keyper set activates. This pre-existing behavior surfaced while reviewing #25515.
KsmEonTracker.readEonAtNewBlockEvent checks for an active keyper set only when currentEon is nil. After learning an eon, an unwind into the earlier interval leaves that cache populated, skips the guard, and calls GetKeyperSetIndexByBlock. Its revert propagates through the tracker and stops the Shutter pool until restart. The existing bind.ErrNoCode handling covers an unwind before deployment, but not this interval.
Reproduction: deploy the manager at block 4, activate the first keyper set at block 10, let the tracker learn that eon, then unwind to block 9. The review reproduction reported get keyper set index by block: execution reverted and pool stopped.
Treat the absence of an active keyper set as a recoverable state, invalidate the relevant cached eons, and resume when activation becomes canonical again. Preserve errors for unrelated contract failures. Add a regression covering the unwind and subsequent recovery. This is operational Shutter behavior; frame-transaction support is not required.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 1.6k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 820
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from erigontech/erigon
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
erigontech/erigon#26523 ·
Maintainers usually reply within 1 day
-
flaky test
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
erigontech/erigon#26230 ·
Maintainers usually reply within 1 day
-
txnprovider/txpool: pending nonce counts past gaps in the poolPossibly taken @yperbasis claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
erigontech/erigon#26014 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
tracing: expose custom error selector and raw payload in callTracer revertReasonPossibly taken @lupin012 claimed this 9 days ago. OpenRPC
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
erigontech/erigon#25928 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
txnprovider/txpool: remove redundant blob/commitment length checkPossibly taken @yperbasis claimed this 14 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
erigontech/erigon#25432 ·
Maintainers usually reply within 1 day
All issues in erigontech/erigon
Similar issues
-
enhancement exporter/awskinesis needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/opentelemetry-collector-contrib#53334 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
SocialGouv/iterion#3376 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
seaweedfs/seaweedfs#12740 · 2 comments ·
Maintainers usually reply within 1 day
-
area:indexer bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#385 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day