celestiaorg / celestiaorg/go-header
store: Give context deadline for flush operation in `flushLoop`
Open
store
- Dominant language
- Go
- Stars
- 21
- Forks
- 33
- Avg merge
- 5d 20h
- Merged PRs (30d)
- 7
Description
Nice, we should actually do the same in the flushLoop in the store.
_Originally posted by @Wondertan in https://github.com/celestiaorg/go-header/pull/52#discussion_r1240223951_
Contributor guide
Research direction
Locate the store's flushLoop and inspect the existing flush operation that this issue says should be handled the same way. Determine where the context deadline belongs, then verify that the flush operation observes it and add or update coverage if the surrounding code provides a relevant test entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100