Source fetching should have a configurable exponential backoff.
Open
- Dominant language
- Python
- Stars
- 140
- Forks
- 45
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
When BuildStream fails to fetch a source, it tries again immediately. It would be a good feature for BuildStream to have an exponential backoff before proceeding to try again, to avoid rate-limiting.
Contributor guide
Research direction
No files or tests are named. Start by locating BuildStream’s source-fetch retry path and the existing configuration mechanism, then identify relevant tests for failed fetches. Done means the retry behavior uses configurable exponential backoff instead of retrying immediately, with tests covering the configured behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100