5 Commits

Include renames

Author	SHA1	Message	Date
magnusandClaude Opus 5	4a2d8fabad	Recover from a btcdata restart without reloading the page ... htmx's WebSocket extension reconnects only after close codes 1006/1011/1012/1013. _ws_proxy closed the browser socket with a normal 1000 on every upstream exit, so htmx read a btcdata restart as a deliberate shutdown and left both panels frozen until the visitor reloaded. New browser connections always worked, which hid the defect from non-browser checks. The proxy now reconnects upstream behind the still-open browser socket on a bounded schedule, resets that schedule after a connection that lasted long enough to count as healthy, and closes with 1012 only once the schedule runs out, so recovery falls back to htmx's own backoff. A concurrent reader detects a departed browser, which a dead upstream would otherwise be indistinguishable from, and an unrenderable payload is logged and skipped rather than ending the stream. tests/test_ws_proxy.py covers this against a real loopback WebSocket server: same socket recovery across an upstream restart for both streams, the retryable close code when the upstream stays down, and skip-on-unrenderable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-10-11 09:21:19 +02:00
magnus	0c86cf3b59	Show midnight change below heading	2026-09-17 14:53:05 +02:00
magnus	b5bbde8acb	Show midnight price change in page title	2026-09-17 14:49:25 +02:00
magnus	6c21f172db	Show live Bitcoin price in page title	2026-09-15 19:51:55 +02:00
magnus	573eba2d86	Prepare btcprice for Kubernetes deployment	2026-09-15 17:12:25 +02:00