mozilla-services / mozilla-services/updatebot
Handle remote clone errors gracefully
Open
Nobody has claimed this yet.
Easy
Enhancement
P3
- Dominant language
- Python
- Stars
- 9
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
We've got 5 of these this month, where git clone fails.
error: RPC failed; HTTP 499 curl 22 The requested URL returned error: 499
fatal: the remote end hung up unexpectedly
Sometimes it's error 502. We could just detect the last line I think.
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
The issue names no source file, test, or entry point. Start by locating the code that invokes git clone and inspect how clone failures are currently reported; reproduce the shown RPC, HTTP 499, or HTTP 502 errors if possible. Done means these remote clone failures are handled gracefully rather than producing an unhandled failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100