Volver al registro de cambios
Interfaz del panel
v4.5.385
The update window no longer stays on "reconnecting" after an update has finished.
Correcciones de errores
4- The update window now closes by itself once the panel backend is back. After an update had finished successfully the window could stay on "reconnecting" until the page was reloaded by hand, and from the outside there was no way to tell whether the update had worked.
- Requests made while the backend is restarting are no longer held open for the life of the page. Holding them is deliberate - it keeps background polls from raising errors behind the overlay during a normal 15-20 second restart - but they were held on a promise that could never complete, so anything waiting on one waited for ever. That is what the update window was waiting on. They are now held only until the backend answers again, with an upper bound.
- A read that was held across a restart is retried with a current token, so it does not come back as a sign-in error immediately after a successful update. Anything that writes is never retried, because it may already have reached the backend before the connection dropped; the page that made the request is told instead.
- The update window health check no longer goes through the panel API client, so it keeps polling regardless of what the client does with ordinary traffic while the backend is away.
Lanzamientos recientes
- Interfaz del panel v4.5.384 nov. 14
- Interfaz del panel v4.5.380 nov. 12
- Interfaz del panel v4.5.379 nov. 10
- Interfaz del panel v4.5.378 nov. 05
- Interfaz del panel v4.5.377 nov. 03
- Interfaz del panel v4.5.376 nov. 03
- Interfaz del panel v4.5.375 nov. 03
- Interfaz del panel v4.5.374 nov. 03