clockworklabs / clockworklabs/SpacetimeDB
Procedures: enable long-running loops which hold non-`SpacetimeType` state in memory
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
E.g. a physics world. This will require:
- On-abort handlers for procedures, so the loop can restart after a crash.
- Proper handling of publishing, i.e. killing the procedure after confirmation and a timeout.
- Changing our database-per-core scheduler to re-home running futures on core-repin, rather than just switching new futures to the new core.
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 procedure lifecycle handling, publishing confirmation and timeout behavior, and the database-per-core scheduler; the issue does not name specific files or tests. Done means procedures can retain non-SpacetimeType state through long-running loops, restart after aborts, terminate correctly after publishing, and re-home running futures during core repinning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100