Concurrent `oasis rofl build` using different deployments
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by tracing the oasis rofl build command through rootfs image creation and temporary-directory handling, then reproduce two builds for different deployments concurrently. Done means concurrent builds no longer clash or publish an old .orc; the separate rofl.yaml race is also noted as a possible additional scope.
Written by the indexing model from the issue text.
Description
It's common when you make a hotfix that you deploy your ROFL simultaneously to Testnet and Mainnet. When building ORCs concurrently, the second one fails with
Validating compose file...
Preparing stage 2 root filesystem...
Runtime hash: e2e074d03ab2fbacaacb01e6d63ce093fde04e4cc620dd8804e8afbb20390525
Creating squashfs filesystem...
Error: failed to create rootfs image: failed to copy file content: write |1: broken pipe
Pushing ROFL app to OCI repository 'rofl.sh/2ef1ae2d-7f04-495d-be0c-35593853dc55:1787832314'...
Pushing... 100.00% [#################################################] 84.53 MiB
And the old version of .orc is pushed.
Figure out where does the clash happen during the creation of rootfs image and make each deployment use unique tmp directory naming.
ps: Another issue is the race condition between two oasis rofl build instances when updating rofl.yaml. This may not be so trivial. Perhaps it would be more convenient for rofl build command to build ROFL for all deployments out there. Then, we could parallelize it easier.
- Dominant language
- Go
- Stars
- 80
- Forks
- 23
- Avg merge
- 9h 43m
- Merged PRs (30d)
- 3
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.
More from oasisprotocol/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
oasisprotocol/cli#709 ·
-
oasisprotocol/cli#717 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
oasisprotocol/cli#707 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
oasisprotocol/cli#704 ·
-
rofl
Difficulty 3/5 1-2 days Newbie friendliness 62/100
oasisprotocol/cli#703 ·
All issues in oasisprotocol/cli
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 60/100
github/gh-aw-mcpg#13748 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
googleapis/librarian#7670 · 2 comments ·