12:40 <sveinse> Is there a way a client/observer can connect to a running bitbake server and receive the events (like knotty.py is)? Is this what the xmlrpcclient.py is for?

12:47 <sveinse> The short story is that I'm running bitbake under a build server and because it's not run in a terminal, knotty only produces log output (which is expected). However the neat progress is lost when not interactive, and I'm concept testing to output the progress over WS. If a net based client exists for events, there's no need to reinvent the wheel...

13:00 <mihai> sveinse: check bitbake's options, there's some hinting in that direction

13:02 <mihai> I'm not sure how it works though, but maybe it helps

13:05 <sveinse> yeah, I'm digging bitbake py code as we speak. There is some logic about a token. If another bitbake is able to connect to a running bitbake build as an observer, then I think this is what I need.

13:25 <sveinse> hmm. Cooker won't accept any remote connections once build has started. This means that it probably wont be trivial to just "tap in" to a running build, as the time from start to build is very short and asynchronous.

13:30 <Saur[m]> sveinse: Toaster is listening to bitbake builds. Though I believe it has to be listening from the start of the build.

13:32 <sveinse> Saur[m]: it is, I think. toaster is starting bitbake in pure server mode, and it doesn't start until the connected client (toaster) tells it to. At least that is how it looks like to me by digging in the code.

13:34 <sveinse> I had hoped to avoid such logic on top and just tap into the ongoing events, but that might not be supported

13:38 <sveinse> Maybe it is just as easy to shoe horn this into knotty.py and send the events from there. Much like what the teamcity.py UI does.