You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
On frontend initialization, when an auto-upgrade is in progress, we want to show an alternative UI for the user to show that a migration is in progress (and its general progress/if there are errors).
Caveats: if the migrator is an init container of the frontend I don't know if anything is running that can expose a port. Maybe we should have a server on the migrator itself rather than the frontend? cc @DaedalusG for input here
cc @Strum355 See #51378 for something you can do for a head-start.
On frontend initialization, when an auto-upgrade is in progress, we want to show an alternative UI for the user to show that a migration is in progress (and its general progress/if there are errors).
Caveats: if the migrator is an init container of the frontend I don't know if anything is running that can expose a port. Maybe we should have a server on the migrator itself rather than the frontend? cc @DaedalusG for input here
cc @Strum355 See #51378 for something you can do for a head-start.