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
After introduction of the PREPARED session status (lablup/backend.ai#2721) to decouple the image pulling process from the container creation process, there are some delays before proceeding to the CREATING status depending on the scheduler invocation frequency and timing.
The current webui (24.12.0-alpha.2.1) does not display the PREPARED sessions in the default "running" sessions tab.
So all new sessions are first displayed as PENDING, they are gone away, and after a while they reappear once they enter CREATING/RUNNING.
I believe we should also display PREPARED sessions, or need to split the view for pre-RUNNING sessions using an additional tab or a separate notification stream.
achimnol
changed the title
Sessions in the PREPARED status are hidden and reappear after scheduling delays, hurting UX
Sessions in the PREPARED status disappear and reappear after scheduling delays, hurting UX
Dec 20, 2024
After WebUI #2854 PR with manager version after 24.12.0 + , the PREPARED session is also showing up in the running session tab. (pending -> preparing -> prepared -> creating -> created -> running)
After introduction of the PREPARED session status (lablup/backend.ai#2721) to decouple the image pulling process from the container creation process, there are some delays before proceeding to the CREATING status depending on the scheduler invocation frequency and timing.
The current webui (24.12.0-alpha.2.1) does not display the PREPARED sessions in the default "running" sessions tab.
So all new sessions are first displayed as PENDING, they are gone away, and after a while they reappear once they enter CREATING/RUNNING.
I believe we should also display PREPARED sessions, or need to split the view for pre-RUNNING sessions using an additional tab or a separate notification stream.
Related:
PREPARED
of session and kernel #2848CREATING
session status #2849The text was updated successfully, but these errors were encountered: