Experiment with generic debouncing code
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
The dispatcher implements debouncing when sending and receiving task updates.
The scheduler implements debouncing on commit events.
We should look into having a common implementation of "coalesce the following events that happen with a gap up to X ms between then, with a maximum latency of no more than Y ms". This could be tested intensively and avoid code duplication.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the dispatcher's debouncing for task updates and the scheduler's debouncing for commit events. Compare their timing behavior and existing tests, then define a shared coalescing implementation with intensive coverage for the gap and maximum-latency limits; done means both callers use it without duplicated logic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100