Open wslabik opened 2 years ago
To validate with the new background callbacks.
@T4rk1n The issue persists with background callbacks the behaviour is different though - it now cannot find functions or modules imported outside the callback
see https://community.plotly.com/t/background-callback-doesnt-work-with-jupyter-dash/78432/12
any workaround for this? where to look for a potential fix?
dash 2.17.0
dash-bootstrap-components 1.5.0
dash-bootstrap-templates 1.1.2
dash-core-components 2.0.0
dash-html-components 2.0.0
dash-loading-spinners 1.0.0
dash-table 5.0.0
Describe your context Please provide us your environment, so we can easily reproduce the issue.
pip list | grep dash
belowDescribe the bug
'running options’ in long callback are not working correctly when used with JupyterDash
Expected behavior
'running options' in long callbacks should work the same way in JupyterDash as they work in regular Dash
Screenshots
Cell output in the jupyter notebook (button is never enabled):![Capture](https://user-images.githubusercontent.com/25907087/168940891-4bbdee1c-d622-4637-a52f-42400cc03831.PNG)
Error which showed in the cell after a while of running:
Here example 2 from the official guide changed to use JupyterDash instead of Dash, where button is never re-enabled (the 'running option' which should been applied at the end of the callback):