tursodatabase/turso

Page modification safety property in the simulator

Open

#4,240 opened on Dec 16, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (1,001 forks)github user discovery
enhancementhelp wantedsimulator

Repository metrics

Stars
 (19,103 stars)
PR merge metrics
 (PR metrics pending)

Description

We had some nasty bugs where page was marked dirty after they were modified:

https://github.com/tursodatabase/turso/pull/4231

https://github.com/tursodatabase/turso/pull/4232

Let's extend the simulator to detect these types of cases. For example, we can calculate a page content hash when we load the page from disk. We can then in add_dirty verify that the hash is unchanged; otherwise someone changed the page without first marking it as dirty. We can make the simulator use the hashes to verify things like rollback safety.

Contributor guide

Research direction
Implement a page content hash when loading pages from disk and verify it in add dirty to detect modifications before marking dirty.
Tech stack
rust
Domain
database
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30