Fix: relay WebSocket messages as text frames (browsers got Blobs they could not parse)

Root cause of 'track does not start': the server re-broadcast incoming frames as
binary (Buffer), so the browser output page received Blobs, JSON.parse failed,
and every command (playTrack, etc.) was silently dropped — only the text-encoded
lastEffect sync got through. Broadcast as text now; net.js also handles Blob
defensively. Also: no-store for app assets + kiosk --disk-cache-size=1 so
redeploys always take effect; /api/clients debug endpoint; /api/peaks duration.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
lucianoandClaude Opus 4.8 committed 2026-06-29 14:58:33 +02:00
1 parent c0230ee1d6
commit 1a66a46b1f
4 files changed
+22 -4

No files matched your search

+1
View File
@@ -11,4 +11,5 @@ exec "$BIN" \
--ozone-platform=wayland \
--ignore-gpu-blocklist \
--test-type \
--disk-cache-size=1 --disable-back-forward-cache \
"$URL" >/tmp/chromium-kiosk.log 2>&1