-
Notifications
You must be signed in to change notification settings - Fork 37.2k
Closed
Closed
Copy link
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseIssue identified as probable candidate for fixing in the next releaseextensionsIssues concerning extensionsIssues concerning extensionsverifiedVerification succeededVerification succeeded
Milestone
Description
Repro steps
I develop an extension which adds a JupyterServerProvider through createJupyterServerCollection. The latest ms-toolsai.jupyter seems to have broken that functionality.
Environment data
- VS Code version: 1.104.2
- Jupyter Extension version (available under the Extensions sidebar): 2023.8.1002501831
- Python Extension version (available under the Extensions sidebar): 2025.14.0
- OS (Windows | Mac | Linux distro) and version: Tested on both Linux and Mac.
- Python and/or Anaconda version: N/A
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
- Jupyter server running: N/A
Expected behaviour
Can register a JupyterServerProvider as before.
Actual behaviour
createJupyterServerCollection is throwing Not Implemented. when called.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
- Create an extension which registers a Jupyter server provider by calling
createJupyterServerCollection. - Launch it.
Logs
Top level log failure: Error: Not Implemented.
I'm also seeing these: this.vscNotebook.onDidChangeNotebookCellExecutionState is not a function.
They both come from the Extension Host logs, since I'm running my extension locally.
Grynn and jaap3
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseIssue identified as probable candidate for fixing in the next releaseextensionsIssues concerning extensionsIssues concerning extensionsverifiedVerification succeededVerification succeeded