oxidecomputer / oxidecomputer/propolis
phd: share single `reqwest` client for all artifact store operations
Open
Nobody has claimed this yet.
enhancement
testing
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
Once #633 lands and removes the use of blocking reqwest clients, the artifact store can have a single client (and thus possibly a single connection pool) that all attempts to download an artifact share. This might save some time on repeated artifact downloads.
Contributor guide
No contributing guide indexed for this repository
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
Review issue #633 first, then trace the artifact store's download operations and their existing reqwest client construction. Confirm how all artifact downloads can use one client and connection pool; done means repeated downloads share that client without blocking reqwest usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100