F: Script continues even when commands fail - #2
Open
@Fardus242 is already working on this.
Since Dec 18, 2025.
bug
- Dominant language
- Shell
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description
The challenge-f.sh script continues executing even when critical commands fail (for example, missing input files or failed file operations).
This can result in misleading “success” messages and make failures harder to detect.
The script must fail fast and clearly when something goes wrong.
Acceptance Criteria
- The script must stop execution immediately when a critical command fails
- Failures must produce clear, human-readable error messages
- Success messages must only be printed if the script completes successfully
- Error handling should remain simple and easy to understand
Notes
- Prefer safe defaults that prevent partial or misleading execution
- Avoid complex control flow or excessive custom error handling
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.
Assessment
This issue has not been assessed yet.