Skip to content

Active/Live Remote Kernel instance is not selected after it is started #9865

Closed
@sbatten

Description

@sbatten

While testing #9768, I was quite confused by the kernel picker UI.

  1. I select "Python 3" unstarted (the only kernel at the start)
  2. I run a cell
  3. The kernel picker says the unstarted kernel is the currently selected kernel
  4. There is a new entry that is the newly started kernel which is truly the currently selected kernel

Perhaps there is a solution in the proxy/lazy kernel work.

Metadata

Metadata

Assignees

Labels

bugIssue identified by VS Code Team member as probable bugnotebook-kernel-pickerupstream-vscodeBlocked on upstream VS code

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions