Specify and verify the system with TLA+
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
mvSQLite has stacked a lot of logic on top of FoundationDB. The *design* of these logic should be verified for correctness.
Some specific subsystems that would benefit from verification:
- The commit path
- Garbage collection
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 mapping mvSQLite’s commit path and garbage collection logic, then identify the FoundationDB-backed behavior that needs formal verification. Define TLA+ specifications for the selected subsystem and establish what properties the verification must prove; the issue does not name implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sqlite
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100