No-need-to-retry errors are still retried in Upload
- Dominant language
- Go
- Stars
- 14
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
https://www.backblaze.com/b2/docs/uploading.html
> 400 Bad Request
> bad_request - message will describe the problem
> cap_exceeded - you have reached the storage cap that you set
> 401 Unauthorized
> missing_auth_token - there is no Authorization header
> bad_auth_token - the authorization token is not valid
> 403 Forbidden
> cap_exceeded - you have reached the storage cap that you set
Contributor guide
Research direction
Start with the Upload entry point and compare its retry behavior with the Backblaze B2 error list in the linked uploading documentation. Check how 400 and 401 errors are classified, including cap_exceeded, missing_auth_token, and bad_auth_token. Done means these no-need-to-retry errors are not retried while retryable upload failures still are.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100