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 by line: Run All should stop RBL session #7718

Closed
Tracked by #5607
bamurtaugh opened this issue Sep 28, 2021 · 6 comments
Closed
Tracked by #5607

Run by line: Run All should stop RBL session #7718

bamurtaugh opened this issue Sep 28, 2021 · 6 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debt Code quality issues notebook-run-by-line
Milestone

Comments

@bamurtaugh
Copy link
Member

Testing microsoft/vscode#133903

  • Start RBL in first cell, get several lines in
  • Click "Run All" at top of notebook while RBL still in progress in first cell
  • 🐛 First cell seems to still be stuck in RBL, while all other cells in the notebook are also trying to run (have the option to stop them)
    • Once I stopped an arbitrary cell in the middle of the notebook, all the cells stopped executing, and RBL stopped in the first cell
    • The output below first cell says "Keyboard Interrupt"
    • I would've expected RBL to stop in first cell (similar to "Continue Execution") and then all other cells to run
    • I've attached the Jupyter output channel logs JupyterRBL9-28.txt
@DavidKutu DavidKutu changed the title Run by line: Run All seems to have halted progress Run by line: Run All should stop RBL session Sep 28, 2021
@DavidKutu
Copy link

What happened was expected. The cells weren't running, they were queued to run after you were done using RBL. The error saying keyboard interrupt is also normal.

Although you make a good point. It would feel more responsive if clicking run all ends the RBL session and starts running immediately.

@roblourens
Copy link
Member

I don't know about that. Why would it be different from the case where a cell is running normally and you click "run all"?

@DavidKutu
Copy link

DavidKutu commented Sep 30, 2021

My answer to that is because this is not only running, its also debugging. But I don't know what would be best, consistent behavior, or more responsiveness.

@DonJayamanne
Copy link
Contributor

I think we should look into what's expected, when user is in rbl can they run cells and vice versa and what the expected behavior.

to me Rbl and running cell are the same, we're still executing code.
It's similar to debugging regular code in vscode and then clicking the debug button again will really in vscode warning the user that a session is already in progress.

@greazer
Copy link
Contributor

greazer commented Sep 30, 2021

Let's do the same thing that we're doing if the user has currently running cells and they try to do run-by-line. We show a messagebox explaining the mode they're in.

@greazer greazer added debt Code quality issues needs-triage and removed needs-triage labels Sep 30, 2021
@greazer greazer added this to the October 2021 milestone Sep 30, 2021
@greazer greazer modified the milestones: October 2021, On Deck Oct 8, 2021
@greazer
Copy link
Contributor

greazer commented Oct 8, 2021

Moving out of October since the workaround is fairly discoverable. Just interrupt executing any of the queued cells. RBL will then be stopped.

@greazer greazer added the bug Issue identified by VS Code Team member as probable bug label Oct 9, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 13, 2023
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 debt Code quality issues notebook-run-by-line
Projects
None yet
Development

No branches or pull requests

5 participants