##// END OF EJS Templates
two-process interactive shell progress...
two-process interactive shell progress * execute payloads (e.g. page/pinfo output) are displayed and paged. * aborted replies don't crash frontend. * intermediate iopub is displayed as it comes * wait for kernel to start before printing first prompt. This gets the right number on the first prompt, and also avoids the log output from being drawn after the first prompt. * protect most of the interact block from keyboard interrupts, which could cause weird errors if ctrl-C was held for a while. * separate restart/wait prompt when kernel dies.

File last commit:

r3970:c5a35798
r5616:7431cd60
Show More
logtopics.rst
13 lines | 454 B | text/x-rst | RstLexer
MinRK
zmq kernels now started via newapp
r3970 =======================
Log Topic Specification
=======================
we use pyzmq to broadcast log events over a PUB socket. Engines, Controllers, etc. can all
broadcast. SUB sockets can be used to view the logs, and ZMQ topics are used to help
select out what to follow.
the PUBHandler object that emits the logs can ascribe topics to log messages. The order is:
<root_topic>.<loglevel>.<subtopic>[.<etc>]
root_topic is specified as an attribute