clockworklabs / clockworklabs/SpacetimeDB
`ProcedureCallError`: preserve distinction between guest and host errors
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Follow-up from #5640 . We'd like to alert, or at least warn, if a procedure call fails with an internal error that traces to a failure in the host, but we don't want to even warn about internal errors due to guest panics.
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 with the ProcedureCallError implementation and the context in issue #5640, then trace how procedure-call failures are classified. The work is done when host-originated internal errors can trigger the requested alert or warning while guest panics remain silent, with tests covering both distinctions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100