The Pi 5 firmware does not rename recovery.bin anymore,
so the check we did to figure out if the updated succeeded
only works on the Pi 4.
related to https://github.com/gokrazy/gokrazy/issues/332
This reverts commit c7823aff1a.
This “fix” introduced a new problem: when navigating in the
back/forward cache, the EventSource connection would not resume.
This should fix occasional hangs when navigating between pages.
I did not expect this behavior from browsers. I would have expected
all pending requests of a page to be terminated when the user
navigates to a different page. Instead, one needs to explicitly
close() EventSource connections.
Currently the status is appended to the service status link and no label
is displayed if the service is running. The status stopped is displayed
with a warning color (yellow). To me this feels uneven and a bit chaotic
which makes it harder to get a good overview and find a service.
This does three things to improve the overview:
- Add a separate column for status label. This takes a bit of width away
from the last log line.
- Color the stopped label less aggressive (gray/default instead of
yellow/warning).
- Add a green label for running service.
Potential improvements for the future could be to show if a service is
enabled/supervised or adding actions like start/stop/restart/enable.
Create a /log endpoint for streaming stdout/stderr logs for processes.
Replace status page stdout/stderr to call into /log to stream logs and
live update page.
Michael Stapelberg
oliverpool
Christian Kugler
Christian Heusel
Anup Chenthamarakshan