Error Handling
- Dominant language
- C++
- Stars
- 10
- Forks
- 8
- Avg merge
- 17d 21h
- Merged PRs (30d)
- 1
Description
We are currently "robust" in the semantic meaning of errors. We return them always to the application and delegate to him decision making. This works well and is robust against exceptions. However, it becomes trickier when we start enabling services.
_Originally posted by @lpottier in https://github.com/llnl/AMS/pull/180#discussion_r2628965075_
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file, test, or entry point is named. Start by reading the error-handling discussion in pull request #180 and map how errors are returned to the application before services are enabled. Done should be a decided, documented error-handling design for service-enabled operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100