Refreshing Session Logs Does Not Maintain The Selected Container

[olevski]

I know the way we handle logs is not ideal and there are many things that can be done to improve things. Especially on the backend.

But one thing will be helpful.

Basically when you select a specific container (not the one selected by default) and then click "Refresh logs" the selected container switches back to the one selected by default.

So it would be nice if the selected container is maintained between refreshes.

There could be cases (in case of restarts) when this may not be possible. Then we can fall back to the default. But when the same session is just starting for a while or failing and nothing has changed. We should not reset the container selection when viewing session logs.

To reproduce:

• launch a session
• wait for more than 1 container to show up when viewing logs
• select the non-default container for the logs
• click refresh logs
• the selected container is not maintained - it always reverts to the same defaul

[olevski]

For example this is what I selected:

Then after clicking refresh logs I get this:

[olevski]

Seen on renku version 2.14.0, UI version 4.17.1

[olevski]

Also the same thing happens on the logs for image builds. And we should remedy that too.

[leafty]

I agree, let's see if we can re-write the log display components to make them more user-friendly.