Progagate errors from C-API
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Currently errors are caught, but not disambiguated. When calls to libfes return a non-zero (or actually 1), there is the option to ask libfes for a clarification using either fes_error (returns string) or fes_errno (returns int/enum). It would be nice to use this functionality to give the user of gofes better errors.
See https://bitbucket.org/cnes_aviso/fes/src/master/C_API.rst for details!
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 by reading the referenced C_API.rst documentation for libfes, especially fes_error and fes_errno. Trace how gofes currently handles non-zero libfes returns and propagate a disambiguated error to callers; done means failures expose the available libfes clarification instead of only a generic error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100