NatLabRockies / NatLabRockies/COMPASS
Mismatching checksum
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 4
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 17
Description
There are a few cases that the checksum (sha256) reported in the jurisdictions.json don't match. This was first noticed by warnings when loading into the DB as well as calculated manually in the shell.
It is interesting that in the full solar run, only 7 failed like that. One txt and 6 PDFs.
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 jurisdictions.json and reproduce the checksum warnings during database loading or by calculating sha256 values in the shell. Compare the reported checksums with the source files from the full solar run, focusing on the one TXT file and six PDFs. Done means the mismatches are explained and the recorded checksums match the files or the underlying data issue is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100