hyper-util: expose connection info on whether it's reused from the pool or newly established
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem? Please describe.
While investigating hard-to-debug connection related issues in cloud infra, we will likely want to obtain any kind of information that might be relevant. Even whether a connection that has just failed is reused from the connection pool or is newly established can be a valuable insight that we could use to troubleshoot.
Describe the solution you'd like
Maybe add a new private field to the hyper_util::client::legacy::connect::HttpInfo, like is_new_connection (or is_reused_connection) and make it publicly accessible via a method?
Describe alternatives you've considered
I didn't come up with other alternatives
Additional context
N/A
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 with hyper_util::client::legacy::connect::HttpInfo and trace how connections from the pool differ from newly established connections. Determine where that state can be retained and exposed without losing information on failed connections. Done means callers can reliably inspect whether a connection was reused or newly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100