You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just noticed the default cell execution timeout changed from 30s in 0.1 to None in 0.2. I realize this is inherited from upstream (jupyter/nbconvert#791) and that I can set a timeout myself, but I thought it might be worth mentioning here. From a UX perspective, at some point the user will get tired of watching the "Executing" spinner and wonder if something is wrong. So, does it make sense for Voila to set its own default? If no, that's fine (as discussed in the nbconvert thread, the "right" number might be different for everyone), but maybe it's worth calling attention to the configuration setting in the docs.
The text was updated successfully, but these errors were encountered:
Voila inherits this setting from nbconvert, and the default is no timeout. This may be undesirable UX in a dashboard, since the user has no indication of whether something has gone wrong or if they just need to keep waiting longer for the notebook to execute and render. Fixesvoila-dashboards#742.
I just noticed the default cell execution timeout changed from 30s in 0.1 to None in 0.2. I realize this is inherited from upstream (jupyter/nbconvert#791) and that I can set a timeout myself, but I thought it might be worth mentioning here. From a UX perspective, at some point the user will get tired of watching the "Executing" spinner and wonder if something is wrong. So, does it make sense for Voila to set its own default? If no, that's fine (as discussed in the nbconvert thread, the "right" number might be different for everyone), but maybe it's worth calling attention to the configuration setting in the docs.
The text was updated successfully, but these errors were encountered: