Python errors don't propagate back to the user
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 17
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Seems like the Python failures (and exceptions) as well as failures in the backend don't
get propagated back to libnomp. Instead, libnomp kernels just prints the wrong answer.
This has to be fixed.
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
No files or tests are identified. Start by tracing how Python exceptions and backend failures move through the kernel runtime to libnomp, then reproduce a failing case; done means those failures reach the user explicitly instead of producing an incorrect answer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- backend, hpc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100