mirror of
https://github.com/tursodatabase/limbo.git
synced 2025-12-23 08:21:09 +00:00
d682f85584
Currently the simulator running on AWS will skip posting issues that are too similar to existing ones, to avoid spamming the issue tracker. However, this loses some information about how frequent a given failure is, so a better solution is to comment on the existing issue whenever a similar failure occurs. Changes: - Track issue numbers alongside titles in openIssues - Add commentOnIssue() to post comments on duplicate issues - Extract shared createFaultDetails() from issue/comment body creation Whole PR written using Opus 4.5 |
||
|---|---|---|
| .. | ||
| bun.lock | ||
| docker-entrypoint.simulator.ts | ||
| Dockerfile.simulator | ||
| github.ts | ||
| levenshtein.test.ts | ||
| levenshtein.ts | ||
| logParse.ts | ||
| package.json | ||
| random.ts | ||
| README.MD | ||
| slack.ts | ||
| tsconfig.json | ||
Limbo Simulator Docker Runner
This directory contains the script that runs inside the limbo-sim Docker image. The script continuously runs the limbo-sim program in a loop until it encounters a panic, at which point it automatically creates a GitHub issue in the limbo repository.
What it does
- The limbo-sim image is built and pushed to ECR by .github/workflows/build-sim.yaml on every main commit
- When the container starts, this script:
- Runs the limbo-sim program with a random seed
- If a panic occurs:
- Captures the seed value and commit hash
- Creates a GitHub issue with reproduction steps
- Includes panic output and relevant metadata
- Continues running with a new seed until a panic occurs or TIME_LIMIT_MINUTES is reached
The script acts as the entrypoint for the Docker container, automatically starting the simulation loop when the container launches.