메뉴
Information about the differential fuzzer tool, how to run it and use it catch bugs in Turso. Always load this skill when running this tool
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/glommer/pgmicro --skill differential-fuzzer명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
How to benchmark and analyze memory usage in Turso using the memory-benchmark crate and dhat heap profiler. Use this skill whenever the user mentions memory usage, memory profiling, allocation tracking, heap analysis, memory regression, memory benchmarking, dhat, or wants to understand where memory is being allocated during SQL workloads. Also use when investigating memory growth in WAL or MVCC mode. IMPORTANT - If you modify the perf/memory crate (add profiles, change CLI flags, change output format, etc.), update this skill document to reflect those changes so it stays accurate for future agents.
How to write tests, when to use each type of test, and how to run them. Contains information about conversion of `.test` to `.sqltest`, and how to write `.sqltest` and rust tests
SOC 직업 분류 기준
| name | differential-fuzzer |
| description | Information about the differential fuzzer tool, how to run it and use it catch bugs in Turso. Always load this skill when running this tool |
Always load Debugging skill for reference
The differential fuzzer compares Turso results against SQLite for generated SQL statements to find correctness bugs.
testing/differential-oracle/fuzzer/
# Basic run (100 statements, random seed)
cargo run --bin differential_fuzzer
# With specific seed for reproducibility
cargo run --bin differential_fuzzer -- --seed 12345
# More statements with verbose output
cargo run --bin differential_fuzzer -- -n 1000 --verbose
# Keep database files after run (for debugging)
cargo run --bin differential_fuzzer -- --seed 12345 --keep-files
# All options
cargo run --bin differential_fuzzer -- \
--seed <SEED> # Deterministic seed
-n <NUM> # Number of statements (default: 100)
-t <NUM> # Number of tables (default: 2)
-c <NUM> # Columns per table (default: 5)
--verbose # Print each SQL statement
--keep-files # Persist .db files to disk
# Run forever with random seeds
cargo run --bin differential_fuzzer -- loop
# Run 50 iterations
cargo run --bin differential_fuzzer -- loop 50
# Build and run from repo root
docker build -f testing/differential-oracle/fuzzer/docker-runner/Dockerfile -t fuzzer .
docker run -e GITHUB_TOKEN=xxx -e SLACK_WEBHOOK_URL=xxx fuzzer
Environment variables for docker-runner:
TIME_LIMIT_MINUTES - Total runtime (default: 1440 = 24h)PER_RUN_TIMEOUT_SECONDS - Per-run timeout (default: 1200 = 20min)NUM_STATEMENTS - Statements per run (default: 1000)LOG_TO_STDOUT - Print fuzzer output (default: false)GITHUB_TOKEN - For auto-filing issuesSLACK_WEBHOOK_URL - For notificationsAll output goes to simulator-output/ directory:
| File | Description |
|---|---|
test.sql | All executed SQL statements. Failed statements prefixed with -- FAILED:, errors with -- ERROR: |
schema.json | Database schema at end of run (or at failure) |
test.db | Turso database file (only with --keep-files) |
test-sqlite.db | SQLite database file (only with --keep-files) |
Always follow these steps
Find the seed in the error output:
INFO: Starting differential_fuzzer with config: SimConfig { seed: 12345, ... }
Re-run with that seed:
cargo run --bin differential_fuzzer -- --seed 12345 --verbose --keep-files
Check output files:
simulator-output/test.sql - Find the failing statement (look for -- FAILED:)simulator-output/schema.json - Check table structure at failure timeCreate a minimal reproducer
.sqltest or in .rs always load Debugging skill for referenceCompare behavior manually: If needed try to compare the behaviour and produce a report in the end. Always write to a tmp file first with Edit tool to test the sql and then pass it to the binaries.
# Run failing SQL against SQLite
sqlite3 :memory: < simulator-output/test.sql
# Run against tursodb CLI
tursodb :memory: < simulator-output/test.sql
| File | Purpose |
|---|---|
main.rs | CLI parsing, entry point |
runner.rs | Main simulation loop, executes statements on both DBs |
oracle.rs | Compares Turso vs SQLite results |
schema.rs | Introspects schema from both databases |
memory/ | In-memory IO for deterministic simulation |
Set RUST_LOG for more detailed output:
RUST_LOG=debug cargo run --bin differential_fuzzer -- --seed 12345