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

"Create Environment"- pressing esc shows the kernel picker again #13503

Closed
DonJayamanne opened this issue May 15, 2023 · 2 comments · Fixed by microsoft/vscode#182919
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug notebook-kernel-picker upstream-vscode Blocked on upstream VS code verified Verification succeeded
Milestone

Comments

@DonJayamanne
Copy link
Contributor

Regression #12240

Other steps to repro:

  • Open kernel picker
  • Select Python Environment
  • Hit escape
  • It will go back to the kernel source picker

@rebornix this is not working again, I noticed this some time ago, but forgot to file an issue or look into this.
Can confirm there's definitely a bug here now as this flow is not right, i can never escape the kernel picker, it always goes back to the Kernel Source Picker

@DonJayamanne DonJayamanne added the bug Issue identified by VS Code Team member as probable bug label May 15, 2023
@DonJayamanne DonJayamanne added this to the May 2023 milestone May 15, 2023
@DonJayamanne
Copy link
Contributor Author

DonJayamanne commented May 15, 2023

@mjbvz this PR is what caused the regression
https://github.com/microsoft/vscode/pull/175603/files

There's no way for commands to throw exceptions now, VS Code seems to swallow them as a result of the above chaneg.

Upstream issue microsoft/vscode#182559

@DonJayamanne
Copy link
Contributor Author

@rebornix is it possble to assume that the kernel picker is supposed to hide if no kernels are returned

					if (selectedKernelId) {
						const { all } = await this._getMatchingResult(notebook);
						const kernel = all.find(kernel => kernel.id === `ms-toolsai.jupyter/${selectedKernelId}`);
						if (kernel) {
							await this._selecteKernel(notebook, kernel);
							return true;
						}
						return true;
					} else {
						return this.displaySelectAnotherQuickPick(editor, false);
					}

I.e. why do we need the else clause here
Lets chat offline

@rzhao271 rzhao271 added the verified Verification succeeded label May 31, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 30, 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 notebook-kernel-picker upstream-vscode Blocked on upstream VS code verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants