ChuckandClaude Opus 5.5 cdaeb3855d fix(web): a refused on-demand start leaves no request in the mailbox ...

POST /api/v3/display/on-demand/start delivered the request (control
socket, else the file mailbox) before it checked the display service.
With the service stopped the socket is absent, so the request went to the
mailbox; the route then answered 400 "Display service is not running"
when start_service was off, or 500 "Failed to start display service" when
the start failed. The display reads that mailbox with max_age=3600 and
never checks a request's timestamp, so the next time it was started it
ran the refused request, pinned if asked.

The service is now checked before anything is delivered, and nothing is
posted when start_service is off and the service is down. When the start
itself fails, the request is withdrawn from the mailbox, but only while
the mailbox still holds this request_id (the compare-before-delete the
display's _consume_on_demand_request uses), so a newer request posted in
the meantime is left for the display.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-03 20:52:39 -04:00

..

api_v3

fix(web): a refused on-demand start leaves no request in the mailbox

2026-10-03 20:52:39 -04:00

__init__.py

Plugins (#145)

2025-12-27 14:15:49 -05:00

pages_v3.py

feat(update): stable/beta update channel; stable follows release tags (#684)

2026-09-30 15:35:26 -04:00