GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — Add setting jupyter.newCellOnRunLast by janosh · Pull Request #7995 · microsoft/vscode-jupyter Conversation
Contributor
For #7966. Went ahead and took a swing at adding a setting to disable appending a new empty cell to IW files when running the last cell. Not sure how successfully tbh. Is
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Rich Chiodo (rchiodo)
approved these changes
Contributor
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Contributor
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
5 of 9 tasks
Member
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Ian Huff (IanMatthewHuff)
self-requested a review
Ian Huff (IanMatthewHuff)
approved these changes
|
There was an error while loading. Please reload this page.
|
Oh, I didn't know about ctrl + enter. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks Janosh Riebesell (@janosh) for the PR. However I'm not yet convinced we should be adding these two settings. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Don Jayamanne (@DonJayamanne) I agree there's no need for #7997 but still think this would be nice to have. Even knowing about ctrl+enter I expect I'll continue to hit shift+enter occasionally out of habit. This then adds new empty cells to files I didn't not mean to modify which in turn causes commit hooks to complain, requiring me to revert the offending files. So I find the current cell-adding behavior a bit of a hassle and would like to disable it completely. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
This one seems different to me. I think we should reopen it. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Codecov Report
@@ Coverage Diff @@ ## main #7995 +/- ## ===================================== - Coverage 70% 70% -1% ===================================== Files 367 367 Lines 22613 22616 +3 Branches 3429 3430 +1 ===================================== - Hits 16041 16032 -9 - Misses 5189 5193 +4 - Partials 1383 1391 +8
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Ooops, sorry I didn't mean to close this, I only meant to update it with my comments. Apologies for that. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Blocking so we discuss this in triage meeting
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Triage agreed to take this
|
Janosh Riebesell (@janosh) we agreed to take this one, but I think it's breaking some of the tests. Specifically this one might be related to your change: Can you try that locally? You can do that inside VS code (if you run with insiders), by running this launch config: And changing the launch config to use a grep: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
You might also just try rebasing against our main branch. Don has fixed a bunch of the tests that were failing. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…JupyterSettings' but required in type 'IWatchableJupyterSettings'
|
Rich Chiodo (@rchiodo) Did the rebase. Workflows awaiting approval. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sadly tests are still failing. They're also difficult to make sense of. "Run tests with VSCode & Jupyter" is the one affected and it has a mile-long output. Not sure what the actual error is. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Close enough. I think those two tests are flakey. Thanks so much for the PR. I'm going to submit. If you happen to help us again, and tests fail, you can look in the publish test results item to see which test failed: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Oh whoops, there's no news item. I'll add a PR shortly with your fix. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Added a commit directly with the news item: Thanks again. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
This setting doesn't actually work, new cells are appended on running the last even when set to const { newCellOnRunLast } = this.configService.getSettings(this.documentManager.activeTextEditor.document.uri); from another place in the code by analogy. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Yeah that looks correct to me. I debugged it a bit. I think the check is in the wrong spot. I believe it should be here:
Instead of passing true for the 'advance' parameter, it should check the setting you added. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Rich Chiodo (@rchiodo) Thanks for taking a look and sorry for getting this wrong. I think the vscode-jupyter/src/client/datascience/editor-integration/codewatcher.ts Lines 1042 to 1048 in 796361a
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Yeah that seems better. I was thinking we only wanted to apply the setting on the SHIFT+ENTER case, but we should apply it on the 'runcell' code lens too (which I believe is the other case that has advance == true) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.