search

winglang / wing

A programming language for the cloud ☁️ A unified programming model, combining infrastructure and runtime code into one language ⚡
https://winglang.io
Other
5.07k stars 198 forks source link

Idea: The Console / Simulator keeps track of the processes created locally #4593

Open skyrpex opened 1 year ago

skyrpex commented 1 year ago

Along with https://github.com/winglang/wing/issues/4583, the Console / Simulator could keep track of the processes instantiated to serve the resources. These processes can be:

The Console would list all of these processes and show which resource manages it. It should also be possible to view each process' logs and see if they ended preemptively (eg, there was an error).

eladb commented 1 year ago

Interesting idea!

I'd start by offering some facilities to start containers and child processes through the simulator context. This will allow reusing the logic but also funnel everything through a central mechanism.

Then we can add some APIs for listing/accessing/collecting logs.

By the way, logs from child/docker should be emitted as log events anyway, so this is aligned!

github-actions[bot] commented 11 months ago

Hi,

This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!

Chriscbr commented 2 months ago

I was thinking about this recently, especially for the dev servers use case.

Maybe it would make sense to have this behind a new flag in the simulator? This way output from these processes can still be converted to traces if you're running the simulator headless (e.g. wing test --debug), but other apps using the simulator like the console can choose how to show the stdout/stderr of various processes on some separate tab or screen perhaps.