From dcf852db49c2dc8ec231968296be16a840c7e834 Mon Sep 17 00:00:00 2001 From: viewit Date: Tue, 7 Jul 2026 01:26:29 +0200 Subject: [PATCH] chore: update nightly changelog --- NIGHTLY_CHANGELOG.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/NIGHTLY_CHANGELOG.md b/NIGHTLY_CHANGELOG.md index 14f29d2..973a812 100644 --- a/NIGHTLY_CHANGELOG.md +++ b/NIGHTLY_CHANGELOG.md @@ -1,7 +1,8 @@ ## Changes in this build -- Refactor: all logs, comments and API error strings translated to English across the codebase (no behavior change) -- Refactor: the `print/start` payload was duplicated in three places and had drifted (the new resonance-compensation setting was missing from the upload+print path) — all print start paths now share one payload builder -- Fix: a couple of silently swallowed errors (dashboard reprint filament-cache load, filament metadata backfill) now log a warning/debug message instead of failing silently +- Fix: the poll interval setting was saved to config.ini but never actually applied — the poll loop always used a hardcoded 3s wait +- Fix: Spoolman status showed a green "connected" dot even when the server was unreachable — reachability is now rechecked periodically and shown accurately (green/red) +- Fix: **settings could silently revert after saving** — the bridge restart that applies settings didn't clean up all the relevant environment variables, so the old value could win over the one just saved (affected poll interval, resonance compensation, Docker host IP, and the new HTTP log toggle below). Fixed at the root so this class of bug can't recur for future settings. +- Feat: new "Log every HTTP request (verbose)" toggle in Settings — off by default, since aiohttp's per-request access log was drowning out the bridge's own logs with the frontend's 2s polling **A stable release is coming soon** with the fixes and features from the last several nightly builds. As usual it will be published as ready-to-run binaries (Linux amd64/arm64, Windows) alongside the Docker image.