limbo/simulator-docker-runner
2025-06-30 11:23:53 +03:00
..
bun.lock Add simulator-docker-runner for running limbo-sim in a loop on AWS 2025-06-02 15:51:29 +03:00
docker-entrypoint.simulator.ts sim/aws: fix vibecoding errors in logic 2025-06-11 08:40:04 +03:00
Dockerfile.simulator Copy sqlite_test_ext to Dockerfile.simulator 2025-06-21 19:51:11 +02:00
github.ts sim/aws: fix vibecoding errors in logic 2025-06-11 08:40:04 +03:00
levenshtein.test.ts Add simulator-docker-runner for running limbo-sim in a loop on AWS 2025-06-02 15:51:29 +03:00
levenshtein.ts Add simulator-docker-runner for running limbo-sim in a loop on AWS 2025-06-02 15:51:29 +03:00
logParse.ts sim/aws: fix vibecoding errors in logic 2025-06-11 08:40:04 +03:00
package.json Add simulator-docker-runner for running limbo-sim in a loop on AWS 2025-06-02 15:51:29 +03:00
random.ts Add simulator-docker-runner for running limbo-sim in a loop on AWS 2025-06-02 15:51:29 +03:00
README.MD Fix URLs to point to github.com/tursodatabase/turso 2025-06-30 11:23:53 +03:00
tsconfig.json Add simulator-docker-runner for running limbo-sim in a loop on AWS 2025-06-02 15:51:29 +03:00

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

  1. The limbo-sim image is built and pushed to ECR by .github/workflows/build-sim.yaml on every main commit
  2. 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.

How do I see the open issues created by the simulator?

GitHub issues