ethereum / ethereum/nodemonitor
Bad block failed
- Dominant language
- Go
- Stars
- 56
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
There was a bad block reported by besu, but it returned a `404` when trying to fetch it

log, probably related:
```
Nov 17 21:48:42 mon04.ethdevops.io nodemon WARN [11-17|20:48:42.057] Failed to write file error="open www/badblocks/0x686c9c3c2a0a1664933e637a23459528aae1107fff5d0cb5cd58b40ce9b60e65.json: no such file or directory"
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the bad-block fetch and file-writing paths associated with www/badblocks/ and the logged missing-directory error. Reproduce the 404 scenario if possible, then confirm the intended handling and verify that bad-block reporting no longer fails when writing the JSON file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100