##// 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:

r17204:b67653df
r20621:f936f880
Show More
logout.html
39 lines | 806 B | text/html | HtmlLexer
{% extends "page.html" %}
{% block stylesheet %}
{{super()}}
<link rel="stylesheet" href="{{ static_url("auth/css/override.css") }}" type="text/css" />
{% endblock %}
{% block login_widget %}
{% endblock %}
{% block site %}
<div id="ipython-main-app" class="container">
{% if message %}
{% for key in message %}
<div class="message {{key}}">
{{message[key]}}
</div>
{% endfor %}
{% endif %}
{% if not login_available %}
Proceed to the <a href="{{base_url}}">dashboard</a>.
{% else %}
Proceed to the <a href="{{base_url}}login">login page</a>.
{% endif %}
<div/>
{% endblock %}
{% block script %}
{{super()}}
<script src="{{static_url("auth/js/logoutmain.js") }}" type="text/javascript" charset="utf-8"></script>
{% endblock %}