Skip to content

Fixing LiveError: Only one live display may be active at once#42

Merged
muellerberndt merged 1 commit into
scabench-org:mainfrom
kevin-valerio:main
Oct 9, 2025
Merged

Fixing LiveError: Only one live display may be active at once#42
muellerberndt merged 1 commit into
scabench-org:mainfrom
kevin-valerio:main

Conversation

@kevin-valerio

Copy link
Copy Markdown
Contributor

This fixes the following bug:

$ python3 hound.py graph build abc --auto
...
LiveError: Only one live display may be active at once

@CLAassistant

CLAassistant commented Oct 7, 2025

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@kevin-valerio kevin-valerio changed the title (fix) Fixing LiveError: Only one live display may be active at once Fixing LiveError: Only one live display may be active at once Oct 7, 2025
@muellerberndt

Copy link
Copy Markdown
Collaborator

Awesome, thanks!

@muellerberndt muellerberndt merged commit dc36008 into scabench-org:main Oct 9, 2025
7 checks passed
zcor added a commit to zcor/hound that referenced this pull request Jun 1, 2026
…a) (scabench-org#42)

Docker single-file bind mounts pin the host inode at container start.
Any rsync/scp/cat> that replaces the host file creates a new inode
invisible to the running container. This silently broke the daily
digest for weeks — the host cron (and subsequent workflow rsyncs) wrote
/opt/hound/beads_summary.json successfully, but the worker container
kept reading the stale inode it captured at startup.

Fix: mount the containing directory, not the file.

- docker-compose.yml: ./state:/config/state:ro (directory mount)
- worker/tasks.py: reader path now /config/state/beads_summary.json
- scripts/update_beads_summary.sh: default OUTPUT under /opt/hound/state/
- deploy/cron.txt: comment + path updated, marks host cron as fallback
- state/.gitkeep: keep the dir tracked in git so compose has something
  to mount locally

Droplet migration: create /opt/hound/state/, move the existing summary
file in, docker compose up -d --force-recreate worker to pick up the
new mount. After that, all writes (rsync, scp, cat>) are visible to
the worker immediately — no restart needed.

CLAUDE.md #62 (new) documents the single-file bind-mount gotcha for
future reference.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants