oasisprotocol / oasisprotocol/cli
`rofl deploy`: Implement ROFL ORC Registry push retry in case of 400 Bad Request error
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 80
- Forks
- 23
- Avg merge
- 9h 43m
- Merged PRs (30d)
- 3
Description
Recently, we had one case at the hackathon where the push to ROFL ORC Registry did not succeed due to 400 Bad Request error.
Error: Failed to push ROFL app to OCI repository: failed to push to remote OCI repository: failed to perform "Push" on destination: PUT "http://rofl.sh/v2/<url>": response status code 400: Bad Request
The 400 Bad Request is usually returned when a token to access the cloud storage expires. This can happen, for example, in the case of a slow network. Currently, the solution is to retry and run the rofl deploy command again. We could mitigate that scenario by introducing a retry to the existing code.
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
Start at the rofl deploy command and locate the existing push to the ROFL ORC Registry. Trace how a 400 Bad Request is handled, then verify that an expired cloud-storage token causes a retry and that a successful push completes without rerunning the command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100