Rename the tooltip defined to run the next line when doing Run By Line

[thegunslingers]

Did search and I believe this is not a duplicate issue.

Environment data

• VS Code version: 1.60
• Jupyter Extension version (available under the Extensions sidebar): v2021.8.2031190714
• Python Extension version (available under the Extensions sidebar): v2021.9.1191016588
• OS (Windows | Mac | Linux distro) and version: Win 10
• Python and/or Anaconda version: Python 3.9
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
• Jupyter server running: Local

Expected behavior

Expected Behavior 1. After Clicking Run By Line the Continue button shows F5 as F5 is a the hotkey to continue
Expected Behavior 2. Clicking the 'Continue button' will continue to execute code until the next break-point.

Actual behavior

Actual Behavior 1. After Clicking Run By Line the Continue button shows F10. F10 steps to the next line like with the normal VScode debugger.
Actual Behavior 2. Clicking the 'Continue button' performs a step over/next (rather than continue)

Steps to reproduce:

1. Open a juypter notebook in VSCode with the vscode-jupyter extension installed
2. Put some python code in a cell
3. Click run by line
4. Hover over the continue button ( observer popup)
5. Click the Continue button (observe a step over / next rather than a continue)

Logs

N/A

Additional Thoughts

It would be helpful to have buttons for Step, Next, Continue etc with the Juypter notebook (think I saw that the roadmap).
Please use the same hotkeys as the VScode debugger (F5 to start debugging (rather than F10), and then F5 continue, F10 next/step over, F11 step in, F11+shift step out.

Also just wanted to say thank you for adding convenient debugging for juypter notebooks! Not having easy (imo) debugging in juypter notebooks has been a big detractor of using juypter notebooks for me personally.

[rchiodo]

Thanks for the suggestion. Full debugging is actually coming to jupyter notebooks too.

What you were using is called Run by line and is slightly different from full debugging (hence why continue is F10, it's the only option). Run by line is literally running one line at a time. You can't use F5 and you can't continue. After interviewing lots and lots of data scientists, run by line was deemed more digestable than full debugging so we did that first.

[rchiodo]

I do think 'Continue' is confusing. We should at least rename it to like 'run next line' or something similar.

[thegunslingers]

That does make sense and I guess there is always an odd man out lol. I agree renaming could be a good solution. Also for what it's worth all the hot keys for full debuging do work after starting a debug session in the version i'm on. (Leave that it in please :) )

[greazer]

Renaming the tooltip makes sense here.

[greazer]

This is already done. The tooltip now says: Run Next Line (F10)