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

run with precedent cells has inconsistent behavior #14554

Open
amunger opened this issue Oct 24, 2023 · 3 comments
Open

run with precedent cells has inconsistent behavior #14554

amunger opened this issue Oct 24, 2023 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug notebook-workflow Issues that interrupt expected or desirable behavior

Comments

@amunger
Copy link
Contributor

amunger commented Oct 24, 2023

Testing #14550

I had 2 cells:

def func2():
    print(3)
func2()
  1. run with precedent cells on the second cell initially only ran the second cell.
  2. after adding x=1 to the first and print(x) to the second run with precedent cells was a noop - no cells ran, no jupyter logs.
  3. After performing a couple more actions, run with precedent cells now runs both cells, even if I revert to the original contents, and reload the window
@amunger
Copy link
Contributor Author

amunger commented Oct 24, 2023

This does not consistently repro

@amunger
Copy link
Contributor Author

amunger commented Oct 24, 2023

got a repro by deleting the precedent cell -> noop
undo to bring the cell back -> still noop

@rebornix
Copy link
Member

run with precedent cells on the second cell initially only ran the second cell.

I think this happens if the first cell is never executed, I have a fix for this #14549 but didn't succeed releasing it yet.

@rebornix rebornix added bug Issue identified by VS Code Team member as probable bug notebook-workflow Issues that interrupt expected or desirable behavior labels Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug notebook-workflow Issues that interrupt expected or desirable behavior
Projects
None yet
Development

No branches or pull requests

2 participants