Some ClientResponseError can't try additional Remotes
Open
Nobody has claimed this yet.
Issue
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: @bmbouter (bmbouter)
Redmine Issue: 4434, https://pulp.plan.io/issues/4434
@gmbnomis pointed out with this comment that a ClientResponseError cannot continue to the next Remote in some cases.
We need to only try additional Remotes if the ClientResponseError is experienced before any data has been streamed to the client.
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 tracing ClientResponseError handling through the path that streams data to the client and determines whether to try additional Remotes. Reproduce a failure before and after streaming begins; done means additional Remotes are tried only when no data has yet been streamed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100