Spamming rebuilds breaks live preview #1

Open
opened 2025-07-13 22:35:00 +00:00 by ficd · 0 comments
Owner

If the user triggers rebuilds in quick succession, the browser is sent the reload command after the first build, even though a second build may be underway. This results in a 404 page being served, and the user needs to manually refresh the browser page.

Mitigation: Don't allow a rebuild until the browser has re-connected to the WebSocket after the first reload.

If the user triggers rebuilds in quick succession, the browser is sent the reload command after the first build, even though a second build may be underway. This results in a 404 page being served, and the user needs to manually refresh the browser page. **Mitigation**: Don't allow a rebuild until the browser has re-connected to the WebSocket after the first reload.
ficd added the
bug
label 2025-07-13 22:35:22 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: ficd/zona#1
No description provided.