##// END OF EJS Templates
Handle kernel messages synchronously...
Handle kernel messages synchronously A problem can happen when two messages come in for different comms, where the second depends on the first (for example, the first might be a message setting the state of a widget, and the second triggering a view creation for the widget). Since comm message queues are independent of each other, the second message could be executed before the first message. This exposes a more fundamental assumption users are likely to have that messages from python are processed synchronously. Thanks to @dmadeka for reporting an error that led to discovering this issue.

File last commit:

r19666:482edf5b
r20621:f936f880
Show More
kernelselector.less
10 lines | 185 B | text/x-less | LessCssLexer
#kernel_logo_widget {
.pull-right();
.current_kernel_logo {
display: none;
.navbar-vertical-align(32px);
width: 32px;
height: 32px;
}
}