erigontech / erigontech/erigon
--chaos.monkey producing non-recoverable error
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 1.5k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 465
Description
`return fmt.Errorf("monkey in the datacenter: %w: %v", consensus.ErrInvalidBlock, txTaskErr)`
`ErrInvalidBlock` - is not recoverable error. Node marking this block as bad and doesn't have other forks to switch. Probably need return some recoverable error. But anyway: current version is useful - for testing how node behave when doesn't have good forks.
Contributor guide
Research direction
Start by locating the --chaos.monkey implementation and the fmt.Errorf call shown in the issue. Trace how consensus.ErrInvalidBlock is classified and how fork handling treats it; the issue provides no file or test names, so confirm the intended recoverable-error behavior before changing anything. Done means the chaos mode's behavior is resolved and covered by the relevant existing test path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, go
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100