icgc-argo / icgc-argo/program-service
Error handling for grpc methods
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3
- Forks
- 0
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 2
Description
-
Pack in the exception into the field
-
Do these need to be defined per field?
-
Right now is failing because databse cant save it
- Identify different types of errors (collisions, conflicts)
- For every call, intercept, if there is an exception, the error gets updated
- OR add an error field for every response
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
The issue does not name files, tests, or entry points. Start by locating the gRPC response definitions and method handlers, then determine how database-save exceptions are currently surfaced. Done should include a decided error representation and consistent handling for the listed collision and conflict cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100