The kernel is still running.  The problem is not the culling of idle 
notebooks.

When I close the browser tab and then reopen the notebook, the kernel is 
still running but output is lost and output from ongoing calculations does 
not appear.  When the ongoing calculations are finished, I can interact 
with the notebook again.

Google tells me that this is a long-standing deficiency of Jupyter.

The (deprecated) SageMath notebook behaves properly on reconnecting, as if 
there was no interruption.

This behavior is indispensable to me, so I can't switch to the Jupyter 
notebook until Jupyter behaves properly when reconnecting.

Daniel

On Wednesday, April 10, 2019 at 7:35:18 PM UTC-4, Nils Bruin wrote:
>
> On Wednesday, April 10, 2019 at 11:19:22 AM UTC-7, Daniel Friedan wrote:
>>
>> However, disconnecting my browser from a remote jupyter notebook aborts 
>> the calculation.
>>
>> That shouldn't need to happen. Jupyter notebook has configuration options 
> for killing "idle" notebooks (for various form of "idle", including "not 
> having a connected browser"):
>
>
> https://jupyter-notebook.readthedocs.io/en/stable/config.html?highlight=idle
>
> In addition, JupyterHub probably has its own ways of culling inactive 
> servers, for various forms of "inactive".
>
> I suspect this is something you'll have to fix in the configuration of 
> JupyterHub, or perhaps in your own jupyter notebook settings.
>
>  
>
>> Is there any way to get reconnectability in the sagemath jupyter notebook?
>>
>> Or should I stick with the deprecated sagemath notebook?
>>
>> thanks,
>> Daniel
>>
>> Daniel Friedan
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to