ERROR: Fatal error in sha256.verify:
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 450
- Forks
- 111
- PR merge metrics
- No merged PRs in 30d
Description
ERROR: Fatal error in sha256.verify:
{
"code": 1,
"stdout": "/tmp/firmware.bin: FAILED\n",
"stderr": "sha256sum: WARNING: 1 of 1 computed checksums did NOT match\n"
}
This is a bug in 'owut/2024.07.31~e329cb9b-r1', please report at
https://github.com/efahl/owut/issues
In anonymous function, file /usr/bin/owut, line 84, byte 24:
called from function [anonymous function] (/usr/bin/owut:280:57)
called from function [anonymous function] (/usr/bin/owut:276:29)
called from function verify_image (/usr/bin/owut:1648:29)
called from function download (/usr/bin/owut:1821:26)
called from anonymous function (/usr/bin/owut:1958:16)
${issue_url}\n);
Near here -------------------^
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 with the /usr/bin/owut stack trace, especially verify_image at line 1648 and the failure reported near line 84. Reproduce the download and checksum mismatch, then trace how download and verify_image handle the sha256sum output; done means the reported verification failure has the intended handling without the shown fatal error.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100