Implement bot compiler and launcher #129

New Issue

2026-08-30T10:22:04+02:00

SirStone commented

2026-08-30 10:22:04 +02:00

Wayfinder child of: #126

Implement compilation of arbitrary .nim bot files and launching them as subprocesses pointed at the running server. Handle compilation errors, process lifecycle, cleanup.

Blocked by: nothing

Grilling Revisions

Compilation: nim c invoked from the garage root directory. The garage's config.nims (with --path:"../common_libs") applies automatically — no explicit path flags needed.

Bot directory generation: Framework auto-generates a temp directory per bot containing:

Compiled binary
JSON config: name from source filename, version: "1.0.0", gameTypes: ["classic"], optional initialPosition
Boot script (one-liner #!/bin/sh\nexec ./binary_name)

Cleanup: temp directories removed after test.

Errors: compilation failure surfaces compiler output clearly, test fails (not silent).

**Wayfinder child of:** #126 Implement compilation of arbitrary .nim bot files and launching them as subprocesses pointed at the running server. Handle compilation errors, process lifecycle, cleanup. **Blocked by:** nothing ### Grilling Revisions **Compilation**: `nim c` invoked from the garage root directory. The garage's `config.nims` (with `--path:"../common_libs"`) applies automatically — no explicit path flags needed. **Bot directory generation**: Framework auto-generates a temp directory per bot containing: - Compiled binary - JSON config: name from source filename, `version: "1.0.0"`, `gameTypes: ["classic"]`, optional `initialPosition` - Boot script (one-liner `#!/bin/sh\nexec ./binary_name`) **Cleanup**: temp directories removed after test. **Errors**: compilation failure surfaces compiler output clearly, test fails (not silent).

SirStone added the wayfinder:task label 2026-08-30 10:22:04 +02:00

SirStone referenced this issue

2026-08-30 10:22:06 +02:00

Implement runBattle() orchestrator #130

SirStone commented

2026-08-30 11:46:11 +02:00

Spec additions from grilling

Use nim c directly, NOT nimble build (nimble swallows compiler output, making errors hard to diagnose).
Compilation timeout: 30s per bot.
Must handle --path flags for common_libs dependencies (e.g. radar_lock).

## Spec additions from grilling - Use `nim c` directly, NOT `nimble build` (nimble swallows compiler output, making errors hard to diagnose). - Compilation timeout: **30s** per bot. - Must handle `--path` flags for common_libs dependencies (e.g. radar_lock).

SirStone referenced this issue

2026-08-30 11:50:56 +02:00

Implement runBattle() orchestrator #130

SirStone commented

2026-08-30 12:05:54 +02:00