BinNormalisationFromECAT8 confusing error message when opening non-existent file
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 160
- Forks
- 113
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
The error message when opening a non-existing file seems to talk about error parsing originating system, as opposed to saying that it cannot open the file.
found by @epapoutsellis
Contributor 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.
Research direction
Start by locating the BinNormalisationFromECAT8 entry point and reproduce its behavior with a non-existent file. Trace the error path and identify the existing test coverage, if any. Done means the failure clearly reports that the file cannot be opened instead of referring to parsing the originating system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100