run_overnight.sh uses wrong Python and tmux window target #137

Closed
opened 2026-02-17 23:20:52 +09:00 by agentson · 0 comments
Collaborator

Problem

Running scripts/run_overnight.sh can fail in two ways:

  1. It defaults to system python3, which may not have project deps (uvicorn missing), so dashboard startup fails.
  2. It targets tmux window :0 explicitly, which breaks when tmux base-index is not 0 (can't find window).

Expected

  • Prefer project venv Python (.venv/bin/python) when available.
  • Keep DASHBOARD_PORT configurable.
  • Target tmux window by name instead of fixed index.

Acceptance Criteria

  • run_overnight.sh defaults to .venv/bin/python if present.
  • DASHBOARD_PORT env var is reflected in launch command.
  • tmux split/layout works regardless of window base index.
## Problem Running `scripts/run_overnight.sh` can fail in two ways: 1. It defaults to system `python3`, which may not have project deps (`uvicorn` missing), so dashboard startup fails. 2. It targets tmux window `:0` explicitly, which breaks when tmux `base-index` is not 0 (`can't find window`). ## Expected - Prefer project venv Python (`.venv/bin/python`) when available. - Keep `DASHBOARD_PORT` configurable. - Target tmux window by name instead of fixed index. ## Acceptance Criteria - `run_overnight.sh` defaults to `.venv/bin/python` if present. - `DASHBOARD_PORT` env var is reflected in launch command. - tmux split/layout works regardless of window base index.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jihoson/The-Ouroboros#137