clockworklabs / clockworklabs/SpacetimeDB
HTTP API generates noisy error logs when calling procedures
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
We're using the HTTP API for some cloudflare worker SSR because the spacetime SDK does not run on cloudflare workers. Recently noticed a ton of errors like
ERROR: my_procedure_name: External attempt to call nonexistent reducer "my_procedure_name" failed. Have you run `spacetime generate` recently?
Notice this error is talking about REDUCERS. All our SSR still works fine so I believe that the name lookup miss on the reducer is leading to the error being logged even though the procedure does fire just fine.
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 HTTP API path for procedure calls and the reducer-name lookup that emits the reported error. Reproduce the call using the HTTP API and observe how a successful procedure invocation is logged. Done means valid procedure calls no longer produce the misleading nonexistent-reducer error while genuine lookup failures remain visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100