celestiaorg / celestiaorg/go-header
sync: cover Head logic with traces
Open
good first issue
- Dominant language
- Go
- Stars
- 21
- Forks
- 33
- Avg merge
- 5d 20h
- Merged PRs (30d)
- 7
Description
Traces will help to quickly identify bottlenecks in the code path if there are any, including for pruning
Contributor guide
Research direction
No files or tests are named. Start by locating the sync Head logic and its pruning path, then inspect how tracing is handled elsewhere in the repository; done means both code paths emit useful traces that can help identify bottlenecks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100