clockworklabs / clockworklabs/SpacetimeDB
Bug: `request_id` not being included in reducer error responses
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Per a report on Discord, the host is not setting the request_id field of TransactionUpdate messages for reducers which errored rather than committing. This should be fixed so that the host sets the request_id field in error responses as well, allowing clients to correlate error responses with requests.
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 by tracing the host code that constructs TransactionUpdate messages when reducers error rather than commit. Follow the reducer error-response path and compare it with successful responses, then verify that clients can correlate the error using request_id. Done means errored reducer responses include the originating request_id.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100