From a495e758fd4fe66eba499c23de1a674e57c890ba Mon Sep 17 00:00:00 2001 From: Jens Ahrensfeld Date: Wed, 1 Jul 2026 20:23:16 +0200 Subject: [PATCH] feat: always write a fixed-name copy of server/sud logs, use .json for sud logs Alongside the dated log files, ServerLogTask/SudLogTask now also write (and overwrite) a fixed-name copy on every write() - logs/log_latest.json and logs/log_latest_sud.json - so a dashboard/tail-style consumer can point at one unchanging path instead of tracking the current run's timestamped filename. Also switches SudLogTask's own dated/latest filenames from .log to .json, matching what they've always actually contained. This incidentally fixes utils/analyze_log.py's two-argument CLI form, which already assumed a .json extension for sud logs. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01JFDeoTKBDkXRhPfnyDEoBt --- README.md | 2 +- tasks/server_log.py | 17 ++++++++++++++--- tasks/sud_log.py | 11 +++++++++-- 3 files changed, 24 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index d694968..93d55fe 100644 --- a/README.md +++ b/README.md @@ -744,7 +744,7 @@ same sample format and `log_interval` checkpointing, but only records while a Sud run is actually active. A fresh run starts recording on a genuine `Start` from `IDLE`/`DONE` (a `Pause`→resume `Start` is a no-op - it's still the same run) and is written out on `Stop` or natural completion (`DONE`), -to `logs/log_T