typelevel / typelevel/cats-effect
Introduce some backoff in the starvation warnings
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
When it triggers it tends to spam for a while. I'm not exactly certain how helpful that is. It definitely makes it hard to ignore, but it's also mostly noise. What we could do is start dynamically increasing the interval whenever it starts firing, up to some bound.
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
The issue does not name a file, test, or entry point; start by locating the starvation-warning implementation and its existing tests. Clarify the intended backoff behavior, including the maximum interval and reset conditions, then verify that repeated warnings become less frequent without removing the warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100