typelevel / typelevel/cats-effect
Make cpu starvation warning's logging destination configurable
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
As mentioned here
This warning log logs directly to System.err, which might be undesirable if the application leverages some custom Logging (i.e Logback, log4cats).
the CpuStarvationCheck should contain a configurable Console(most likely through IORuntimeConfig) .
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 locating CpuStarvationCheck and IORuntimeConfig, then trace where the warning is written to System.err. Determine how a configurable Console could be supplied for custom logging, and verify that the CPU starvation warning uses that destination without changing other runtime behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100