38ea9b3d06488a9decff68c23997ba308e593b0d
CI / test (push) Has been cancelled
When the firmware sends X-Draw-Pending: 1, its drawNeeded NVS flag survived a power-loss-during-draw — it has the bytes for the previous image in its cached /img.bin and just needs another chance to finish painting them. Return the device's current image (no rotation advance), which lands as a 304 since the device claims the same image-id. Crucially this overrides the X-Boot-Reason: cold force-resync. The typical mid-draw-interruption cause IS a reset that turns the next wake into a cold boot, so without this override force-resync chases a fresh image every interruption and the device cycles through the rotation leaving torn frames on the 13.3 panel. Locked image still wins (user intent overrides recovery). Old firmware that doesn't send the header is unaffected — branch is gated on the header being present. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Description
pictureFrame web app — Symfony + Vue SPA
Languages
Python
42.9%
PHP
20%
HTML
12.5%
TypeScript
11.7%
Vue
7.6%
Other
5.3%