Bootstrap: wrap script in main() to guard against partial curl | bash downloads
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 83/100
Research direction
Read scripts/bootstrap.sh and the README's installer command to understand how the script is used. Wrap its executable body in main() and call main "$@" at the end; done means the downloaded script's logic runs only after the complete file has arrived.
Written by the indexing model from the issue text.
Description
Summary
The README recommends curl … bootstrap.sh | bash. scripts/bootstrap.sh runs its logic at top level, so a connection cut mid-download could execute a partial script.
Proposal
Wrap the executable body in a main() function and call main "$@" on the last line, so nothing runs unless the whole file has arrived. This is the standard pattern for pipe-to-shell installers.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- Avg merge
- 16m
- Merged PRs (30d)
- 40
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 graygarbage/HermesKey
-
enhancement future consideration privacy
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
graygarbage/HermesKey#92 ·
Maintainers usually reply within 1 day
-
enhancement future consideration
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
graygarbage/HermesKey#89 ·
Maintainers usually reply within 1 day
-
enhancement experimental privacy
Difficulty 5/5 Over a week Newbie friendliness 35/100
graygarbage/HermesKey#96 ·
Maintainers usually reply within 1 day
-
documentation enhancement future consideration
Difficulty 4/5 3-5 days Newbie friendliness 45/100
graygarbage/HermesKey#95 ·
Maintainers usually reply within 1 day
-
future consideration packaging
Difficulty 4/5 3-5 days Newbie friendliness 45/100
graygarbage/HermesKey#93 ·
Maintainers usually reply within 1 day
All issues in graygarbage/HermesKey
Similar issues
-
fix(backup-uploader): write current-round marker outside / so the container can run as non-rootOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hiero-ledger/solo-containers#254 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CachyOS/cachyos-hooks#23 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
bug cli security sev-6
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
area/cli good first issue size/S type/feature
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
lorica-labs/volant#549 ·
Maintainers usually reply within 1 day