clockworklabs / clockworklabs/SpacetimeDB
Improve error when schedule a reducer with duration > 2 years
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
We get a crash when you try to schedule a reducer and you pass a duration that is very far in the future, we should have an actual error message for this.
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
Locate the reducer scheduling entry point and reproduce the crash with a duration more than two years in the future. Trace where the duration is rejected or overflows, then replace the crash with an actual error message and verify the long-duration case no longer crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100