hermes-admin/hermes-agent
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

fix: the dashboard reads update.log through the one log-path resolver

Browse Source 
The status route rebuilt <root>/logs/update.log by hand while
hermes_cli.logs.log_file_path("update") already owns that placement (root
home for the update tee). One resolver, so a future move cannot split the
writer and this reader.
This commit is contained in:
Teknium
2026-10-05 22:35:58 -07:00
parent 0b5b01ba7a
commit 7cff855c8a
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
hermes_cli/web_routers/actions.py
View File

@@ -379,10 +379,9 @@ async def get_action_status(name: str, lines: int = 200):
if name == "hermes-update":
# ``hermes update`` mirrors to the ROOT home's update.log (main_dashboard), never this
# dashboard's profile home: read it where it is written.
from hermes_constants import get_default_hermes_root
from hermes_cli.logs import log_file_path
durable_update_action_id = _durable_completed_update_action_id(
_tail_lines(get_default_hermes_root() / "logs" / "update.log", 2000))
durable_update_action_id = _durable_completed_update_action_id(_tail_lines(log_file_path("update"), 2000))
spawned_action_id = (_latest_spawned_update_action_id(_tail_lines(log_dir / log_file_name, 2000))
or _persisted_action_id(log_dir, name) or _ACTION_IDS.get(name))
if durable_update_action_id != spawned_action_id: