[BUG] exo run receives all logs

[BenElgar]

Describe the bug
When running exo run you get all of the logs for the history of the workspace, not just the logs for the processes you just started.

[brandonbloom]

Is this still true? And what precisely would you expect to happen?

It's not at all obvious what the right thing to do for logs of old components. Seems like you'd want logs to be somewhat immutable, but if you are applying a filter to set of components and a component changes... you probably want those filtered out.

If we can lock down what we think the best possible behavior is here, we can probably improve this. I suspect whatever improvements we do make though will have to wait until after we improve the system to be more event-driven.

[BenElgar]

Yes, it appears to still be true.

My expectation when running exo run would be that it only displays logs for the current run. I wouldn't expect it to display any historical logs. I don't necessarily have an issue with it displaying logs of old components so long as those components are actually running.

[brandonbloom]

Ah, OK - I understand now. I think this might get implicitly fixed after we implement support for "stacks", since my tentative plan is for run to create a temporary/isolated stack, which will solve a bunch of the complexities around interactions between the gui, start, stop, event handling, etc. In such a world, each stack would have unique component ids, and therefore unique streams, so there would be no scrollback.