Skip to content
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

Closed
keluc opened this issue Aug 7, 2020 · 6 comments
Closed

Settings Stop on Error not working #736

keluc opened this issue Aug 7, 2020 · 6 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@keluc
Copy link

keluc commented Aug 7, 2020

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)?

image

Steps to cause the bug to occur

  1. Enable the setting "Data Science: Stop On Error. Stop running cells if a cell throws an exception"
  2. Create new Jupyter notebook with 3 cells (1st and 3rd cell a print statement, 2nd cell raise an exception)

Actual behavior

  1. All cells are executed

image

Expected behavior

  1. Execution stops after the 2nd cell like in the jupyter notebook interface.

image

Your Jupyter and/or Python environment

  • Jupyter server running: Local
  • Extension version: 2020.7.96456
  • VS Code version: 1.47.3
  • Setting python.jediEnabled: true
  • Setting python.languageServer: Jedi
  • Python and/or Anaconda version: winpython 3.7.7
  • OS: Windows | Mac | Linux (distro): Windows
  • Virtual environment: N/A
@claudiaregio
Copy link
Contributor

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"

@keluc
Copy link
Author

keluc commented Aug 10, 2020

not at first but I've tried it several times but it doesn't seem to change anything.

@claudiaregio
Copy link
Contributor

Ok, we will take a look into this, thanks!

@stonebig
Copy link

same here on WinPython-3.8.5.0rc / vscode-1.48.0 / python-vscode-2020-8-101144

image

@keluc
Copy link
Author

keluc commented Aug 17, 2020

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.

image

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.

image

Is this behaviour caused by the same issue?

@IanMatthewHuff IanMatthewHuff self-assigned this Aug 17, 2020
@rchiodo
Copy link
Contributor

rchiodo commented Aug 20, 2020

Validated. Will be in our next major release.

@rchiodo rchiodo closed this as completed Aug 20, 2020
@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode-python Nov 11, 2020
@DonJayamanne DonJayamanne added bug Issue identified by VS Code Team member as probable bug reason-regression labels Nov 11, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

6 participants