clockworklabs / clockworklabs/SpacetimeDB
Classify view evaluation and materialization failures
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 https://github.com/clockworklabs/SpacetimeDB/pull/5640.
InstanceCommon::call_view_with_tx in crates/core/src/host/wasm_common/module_host_actor.rs, view result parsing, guest-returned SQL, constraint violations while writing returned rows, and internal datastore failures share one anyhow::Error log path.
Audit whether these errors can retain enough classification for guest-caused failures, such as invalid results or duplicate primary keys, to use guest logs at warn! or lower while genuine backing-table or datastore failures use error!.
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 InstanceCommon::call_view_with_tx in crates/core/src/host/wasm_common/module_host_actor.rs and review the changes in pull request 5640. Trace view result parsing, guest-returned SQL, constraint violations while writing returned rows, and internal datastore failures through their shared anyhow::Error path. Done means guest-caused failures retain enough classification for warn! or lower, while genuine backing-table or datastore failures remain error!.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, observability
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100