The deployment check needs sha256sum, which macOS does not have
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start in scripts/verify-deployment.sh, where sha256sum --check --status is called at line 19 and sha256sum "$fetched" at line 30. Pick the hashing tool once at the top, falling back to shasum -a 256, and check the fixture tests/fixtures/access_policy.wasm.sha256, which both tools read. Run bash -n on the script, then simulate macOS by hiding sha256sum from PATH on Linux. Done when both tools give the same output and a mismatched fixture still exits 1.
Written by the indexing model from the issue text.
Description
Written against commit 78d0a89; later commits may have moved things, so check the code first.
Size: Trivial
Description
scripts/verify-deployment.sh uses sha256sum --check --status (line 19) and sha256sum "$fetched" (line 30). macOS ships shasum (shasum -a 256) and no sha256sum unless coreutils is installed, so on a Mac the first command of the README's "Run it, from nothing" section fails with sha256sum: command not found. The README says Windows users should use WSL and says nothing about macOS, but the script otherwise only needs bash and the Stellar CLI, which both run on a Mac.
Current state
scripts/verify-deployment.shlines 19 and 30.tests/fixtures/access_policy.wasm.sha256is insha256sumformat (<hash> <file>), whichshasum -a 256 -calso reads.
What to build
Pick the tool once at the top (sha256sum if present, else shasum -a 256, else the missing-tool message from the sibling issue) and use it for both the check and the hash. Keep the output and exit codes the same.
Acceptance criteria
- The script gives the same output with either tool (show both, even if you can only run one for real: say which you could not run).
- A fixture that does not match the pin still exits
1with the same message. -
bash -n scripts/verify-deployment.shpasses.
Out of scope
Windows without WSL.
Verification
bash scripts/verify-deployment.sh on Linux; on macOS, or with sha256sum hidden from PATH on Linux (env PATH=...).
- Dominant language
- Rust
- Stars
- 2
- Forks
- 2
- Avg merge
- 49m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from Sorogate/example-consumer
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Sorogate/example-consumer#17 ·
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Sorogate/example-consumer#16 · 1 comment · 1 reaction ·
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Sorogate/example-consumer#15 ·
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Sorogate/example-consumer#14 ·
-
enhancement good first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 80/100
Sorogate/example-consumer#12 ·
All issues in Sorogate/example-consumer
Similar issues
-
defect
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
enhancement user-priority/P3
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day