New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Settings Stop on Error not working #736
Comments
hi @keluc , did you reload the window after changing the setting? You can do so by pressing Ctrl + Shift + P and selecting "Developer: Reload Window" |
not at first but I've tried it several times but it doesn't seem to change anything. |
Ok, we will take a look into this, thanks! |
In addition to the issue described above, if you execute a number of cells above a certain cell and those take some time to be executed (indicator [*]), you can execute the last cell and this one gets a prompt number before the other cells are finished. If you execute all from the beginning it seems to execute in the correct order (at least the number of times I tried) In the jupyter notebook or lab the execution order is always maintained. Is this behaviour caused by the same issue? |
Validated. Will be in our next major release. |
Bug: Notebook Editor
In the extension settings there is an option "Data Science: Stop On Error. Stop running cells if a cell throws an exception" (python.dataScience.stopOnError).
Is this option not intended to handle errors like in the Jupyter notebook interface (stop execution in the cell causing the error)?
Steps to cause the bug to occur
Actual behavior
Expected behavior
Your Jupyter and/or Python environment
The text was updated successfully, but these errors were encountered: