clockworklabs / clockworklabs/SpacetimeDB
Make `--data-dir` and `--in-memory` mutually exclusive
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Right now you can't actually run spacetimedb-standalone in memory even though we have an --in-memory flag.
We need to fix the --in-memory flag to not ever access disk, and we also need to then make the --data-dir and --in-memory flags mutually exclusive.
This should be done by creating the appropriate interface for accessing the "storage" layer and ensure that all access goes through that interface.
NOTE: This is likely a prerequisite for Deterministic Simulation Testing of the whole process.
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 spacetimedb-standalone entry points for --data-dir and --in-memory, then identify every storage access that can reach disk. Define the storage interface and verify that in-memory mode never accesses disk and that the two flags cannot be used together.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100