stdout output after launch is lost when opening the wx UI

[mikeal]

Basically if something happens like, the server can't bind the proper port, or something loads improperly when starting the wxUI we never see it.

We need to wrap stdout right when windmill starts and then once the wxUI shell is up dump it all into the shell window.

[jacob]

Replying to mikeal:

Basically if something happens like, the server can't bind the proper port, or something loads improperly when starting the wxUI we never see it. We need to wrap stdout right when windmill starts and then once the wxUI shell is up dump it all into the shell window.

So are you suggesting that windmill store all the output information when it starts in a dictionary or something then after starting the wxui, all the info is dumped into the log output section?

[mikeal]

What we can do, is when the wxui option is present, replace the sys.stdout and sys.stderr objects with a StringIO instance.

Once the wxui loads up, we can then set sys.stdout and sys.stderr back to sys.stdout and sys.stderr, and dump what's in the StringIO instances in to the wxui.