Add robust exceptions to Python client
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 304
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
Currently the Python client does not have a robust and friendly exception classes and throws a **Segmentation fault** error on the erratically formatted schema files and this error, which does not do a good job at hinting what goes wrong:
```shell
terminate called after throwing an instance of 'std::runtime_error'
what(): Not a number.
Aborted (core dumped)
```
We should add some important exception classes to the client with more information that handle the lower-level errors bubbling up to the caller.
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 Python client and the lower-level schema parsing path that produces the shown runtime error or segmentation fault. Define the exception classes and information needed from the issue context, then verify that malformed schema files produce useful client-facing errors instead of terminating the process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100