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

Epoch cache error should be treated with care in gossips validation #5938

Closed
nazarhussain opened this issue Sep 6, 2023 · 0 comments · Fixed by #5939
Closed

Epoch cache error should be treated with care in gossips validation #5938

nazarhussain opened this issue Sep 6, 2023 · 0 comments · Fixed by #5939
Assignees
Labels
meta-bug Issues that identify a bug and require a fix. scope-logging Issue about logs: hygiene, format issues, improvements. scope-ux Issues for CLI UX or general consumer UX.

Comments

@nazarhussain
Copy link
Contributor

Describe the bug

Issues regarding gossip validations

Error: Requesting slot committee out of range epoch: 113739 current: 113737
    at EpochContext.getShufflingAtEpoch (file:///usr/app/packages/state-transition/src/cache/epochContext.ts:720:13)
    at EpochContext.getShufflingAtSlot (file:///usr/app/packages/state-transition/src/cache/epochContext.ts:709:17)
    at getCommitteeIndices (file:///usr/app/packages/beacon-node/src/chain/validation/attestation.ts:287:56)
    at validateGossipAttestation (file:///usr/app/packages/beacon-node/src/chain/validation/attestation.ts:91:28)
    at validateGossipAttestationRetryUnknownRoot (file:///usr/app/packages/beacon-node/src/network/gossip/handlers/index.ts:349:14)
    at beacon_attestation (file:///usr/app/packages/beacon-node/src/network/gossip/handlers/index.ts:182:28)
    at JobItemQueue.gossipValidatorFn [as itemProcessor] (file:///usr/app/packages/beacon-node/src/network/gossip/validation/index.ts:84:7)
    at JobItemQueue.runJob (file:///usr/app/packages/beacon-node/src/util/queue/itemQueue.ts:92:22)

non-GossipActionError reported by Micah

Aug-11 07:37:06.001[]                 info: Synced - slot: 3641285 (skipped 2) - head: 3641283 0xfbcb…edb2 - execution: syncing(0x0631…0396) - finalized: 0xb07e…a3e6:113787 - peers: 47
Aug-11 07:37:18.000[]                 info: Synced - slot: 3641286 - head: 3641286 0x20b6…cf2a - execution: syncing(0xe143…c4d6) - finalized: 0xb07e…a3e6:113787 - peers: 47
Aug-11 07:37:24.112[NETWORK]         error: Gossip validation beacon_aggregate_and_proof threw a non-GossipActionError  Requesting slot committee out of range epoch: 113790 current: 113788
Error: Requesting slot committee out of range epoch: 113790 current: 113788
    at EpochContext.getShufflingAtEpoch (file:///usr/app/node_modules/@lodestar/state-transition/src/cache/epochContext.ts:669:13)
    at EpochContext.getShufflingAtSlot (file:///usr/app/node_modules/@lodestar/state-transition/src/cache/epochContext.ts:658:17)

Expected behavior

Such errors are very aggressive to logs.

Steps to reproduce

No response

Additional context

Extracted this issue from action points of the main epic.

Operating system

Linux

Lodestar version or commit hash

1.11.x

@nazarhussain nazarhussain added scope-logging Issue about logs: hygiene, format issues, improvements. scope-ux Issues for CLI UX or general consumer UX. meta-bug Issues that identify a bug and require a fix. labels Sep 6, 2023
@nazarhussain nazarhussain self-assigned this Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta-bug Issues that identify a bug and require a fix. scope-logging Issue about logs: hygiene, format issues, improvements. scope-ux Issues for CLI UX or general consumer UX.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant