Improve error reporting for application exceptions thrown in the initialization phase.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
Currently, for exceptions thrown in the initialization phase of an application:
- Stack traces are not included in the error message.
- The error is not aggregated to Kafka.
For example I got a confusing error message:
2022-01-03T10:15:43.468764Z ERROR blueboat::ctx: native invoke error from app ***.tar] request "unknown": expected type `v8::data::Uint8Array`, got `v8::data::Value`
Due to an undefined being passed to new TextDecoder().decode().
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
Trace initialization-phase exception handling from the blueboat::ctx error path and inspect how errors are currently reported and aggregated to Kafka. Confirm the behavior with an initialization exception such as the undefined value passed to TextDecoder.decode(); done means the error includes a stack trace and is aggregated to Kafka.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, kafka, rust
- Domain
- backend, distributed-systems, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100