mirror of
https://github.com/screentinker/screentinker.git
synced 2026-08-13 22:03:13 -06:00
067aebfd75
A fixed OTA_DOWNLOAD_MAX_CONCURRENT=10 throttled a legitimate coordinated rollout even on a perfectly healthy server, and a shed 503 costs a client a full ~30-min re-check cycle. Made the download guard's concurrency + rate caps band-aware: - normal -> serve FREELY (no cap): a whole-fleet rollout isn't staggered when healthy - elevated -> the configured caps engage (early backpressure) - critical -> shed 503 (the real protection, unchanged) Kill switch OTA_DOWNLOAD_GUARD_ENABLED=false disables it entirely. Tests updated: normal serves 50/50 with 0 shed; caps + shed now asserted under elevated; storm harness OTA flood runs under elevated (the loaded state). Suite green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| config | ||
| db | ||
| lib | ||
| middleware | ||
| player | ||
| routes | ||
| scripts | ||
| services | ||
| test | ||
| ws | ||
| .gitignore | ||
| config.js | ||
| package-lock.json | ||
| package.json | ||
| server.js | ||
| version.js | ||