Add more (DEBUG) logging for client-side pools
Open
1 - triaged
t:client
t:core
- Dominant language
- Scala
- Stars
- 1.4k
- Forks
- 584
- Avg merge
- 14h 33m
- Merged PRs (30d)
- 24
Description
* when connections are closed
* when automatic retries happen
Contributor guide
Research direction
Start by locating the client-side pool code paths where connections close and automatic retries occur, then inspect nearby logging patterns. Done means both events emit useful DEBUG-level messages and the relevant pool tests still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100