It would be nice to have a debug mode that logs lots of things to the JS console.<div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 8, 2012 at 12:45 AM, Matthias BUSSONNIER <span dir="ltr"><<a href="mailto:bussonniermatthias@gmail.com" target="_blank">bussonniermatthias@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Dave,<br>
<br>
Happy to see you might have find a solution.<br>
<br>
I'll see if I can come up with a notebook that auto execute during lunch break so that you don't have to manually press shift enter.<br>
I think it might need some code tweak on server side, so maybe we could design a 'diagnostic' mode for the notebook, that just<br>
pop up a page that constantly probe the kernel connexion and report the status of different actions.<br>
<br>
Good luck for debugging,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Matthias<br>
<br>
Le 8 nov. 2012 à 06:09, David Hume a écrit :<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
> Hi all, thanks very much for the feedback so far.<br>
><br>
> My colleagues (who's computers run in our corporate Windows environment)<br>
> have had no notebook access for the best part of a week (poor windows<br>
> users...)<br>
><br>
> So today, in frustration (and out of sympathy on my part) we started a trial<br>
> and error procedure of removing processes, one by one, from one of the<br>
> windows machines in question.<br>
><br>
> Our procedure was this:<br>
><br>
> while notebook does not return an output:<br>
> remove a process (being careful to not kill any system processes)<br>
> close/kill any open iPython and the web browser sessions (note:<br>
> restarting the kernel was not enough)<br>
> re-run iPython notebook with new web browser session<br>
> Shift enter in a code cell<br>
><br>
> Doing this we have managed to get the windows notebook back up and running!<br>
><br>
> We just haven't quite nailed down the exact process which is causing this<br>
> (as we did this in batches to save time....)<br>
><br>
> Oddly, if we reboot the machine and quickly open the iPython notebook we can<br>
> obtain a working notebook. If we restart the kernel a few minutes (maybe<br>
> seconds?) later the notebook output stops.<br>
><br>
> I think we almost have this nailed.<br>
><br>
> I'll post here again tomorrow, once we track the exact rogue process/program<br>
> that is causing this mischief.<br>
><br>
> cheers<br>
> Dave Hume<br>
> Wellington, NZ.<br>
><br>
><br>
><br>
><br>
><br>
> --<br>
> View this message in context: <a href="http://python.6.n6.nabble.com/Re-Notebook-cells-don-t-execute-in-Windows-tp4994309p4995181.html" target="_blank">http://python.6.n6.nabble.com/Re-Notebook-cells-don-t-execute-in-Windows-tp4994309p4995181.html</a><br>
> Sent from the IPython - User mailing list archive at Nabble.com.<br>
> _______________________________________________<br>
> IPython-User mailing list<br>
> <a href="mailto:IPython-User@scipy.org">IPython-User@scipy.org</a><br>
> <a href="http://mail.scipy.org/mailman/listinfo/ipython-user" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-user</a><br>
<br>
_______________________________________________<br>
IPython-User mailing list<br>
<a href="mailto:IPython-User@scipy.org">IPython-User@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-user" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-user</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Brian E. Granger<br>Cal Poly State University, San Luis Obispo<br><a href="mailto:bgranger@calpoly.edu" target="_blank">bgranger@calpoly.edu</a> and <a href="mailto:ellisonbg@gmail.com" target="_blank">ellisonbg@gmail.com</a><br>
<br>
</div>