clockworklabs / clockworklabs/SpacetimeDB
Update `bad {} signature for {:?}` error message for ill-typed module exports
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Error: bad call_reducer signature for "__call_reducer__"; expected FuncSig { params: [I32, I32, I32, I64, I32], results: [I32] } got FuncSig { params: [I32, I32, I64, I32], results: [I32] }
This error almost always means a bindings dependency which doesn't match the host version. We should update the error message to point users in that direction, with text like, "Does your module's spacetimedb dependency match the server's SpacetimeDB version?"
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
Search the repository for the exact bad call_reducer signature error text and inspect how the ill-typed module export error is assembled. Update the message to point users toward matching the module's spacetimedb dependency with the server version, then verify that the revised guidance appears for this signature mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100