-
Notifications
You must be signed in to change notification settings - Fork 297
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
Jupyter cannot connect to a remote server using a custom ServerPicker #13112
Comments
Tagging @DonJayamanne since they wrote the module I base my code off :) |
@mtreca
|
Hi @DonJayamanne, thank you for your reply! I followed the steps you mentioned, but I do not think the output changes a lot:
|
@mtreca I will need to build a custom version of the VSIX with additional logging to see whats going on |
Thanks! |
Thanks, unfortunately I'm not entirely sure I understand this statement. |
Hi again. Sorry for the delay and not being clear in my last message. Regardless of how I define the remote server configuration, the baseUrl defined by my kernel picker is always equal to "https://remote/", which seems to be hardcoded in the Jupyter extension. So I guess my custom kernel picker does not properly pass the remote url to the Jupyter extension. After thinking about it, I would also be happy with a much simpler mechanism which would just allow my extension to write URLs to the "Existing Jupyter Servers" section of the Kernel Picker (i.e. as if the user had manually entered this url before). No need to define a custom kernel picker in this case. Do you know if such a thing is possible? Thanks a lot for your help! |
I recently fixed a few issues and also created a sample extension that uses this api Let met know goes that goes Thanks for your patience |
Good to hear, thanks for the quick update! My work env does not let me use insiders or pre-release. Will test when the new version of the plugin is released then! Will keep you updated, thanks |
I haven't tried using a custom Jupyter hub though, will try that soon |
Found a few issues and have addressed them, however it will take a while to ship those fixes, will keep you posted. |
This should be addressed in the latest pre-release version, please let me know how that goes |
Hi @DonJayamanne 👋 I'm using the pre-release version and followed your steps above, deleting any existing connections + reload, and I'm still hitting this issue. Maybe I'm using the API incorrectly but the
Any suggestions or further debug information that would help you?
It'd be super useful to see that code and be sure I'm using the API as expected! 😄 |
I’m sorry you are running into this |
Thank you @DonJayamanne , your responsiveness is most appreciated! 🥇 |
Just and update for everyone here, we're working on stabilizing the API in the current iteration I will post the sample later once we have a stable API, this prevents issues with users using an old API and then having to switch again to another API. |
@brandonjbjelland are you still running into this issue with the current API. |
I'd put the component that depended on this functionality on hold until hearing back. I'll dig back in within a week or so. Thanks @DonJayamanne ! |
A new API has been published and this new API will be available for use in the next version of the Jupyter exetnsion (to be published sometime this week). Here's a sample https://github.com/microsoft/vscode-extension-samples/tree/main/jupyter-server-provider-sample |
You can try this new API in vscode insiders + pre-relese version of the Jupyter extension, Do let me know how things go, |
Hi again! Thanks a lot for working on this feature and providing an example use of your new API. Following your example works really nicely and the ability to add custom functions is also appreciated. I managed to get the new registration API working pretty quickly. |
This happens if you had connected to Jupyter hub from within the Jupyter extension in the past;
We have created a new |
Thats great new, please do let me know if you run into any issues. |
That fixed it, thanks again! |
Applies To
What happened?
Hi there!
I created a custom VSCode extension in order to interact with my company's remote JupyterHub clusters, based on the examples provided on your repository here. My extension defines, among other things, a custom Jupyter Server Picker which is then registered with the Jupyter extension.
The custom server picker is registered and functions properly since it is properly displayed when clicking the
Select kernel
button after activating my extension. The Server picker also seems to return properIJupyterServerUri
objects, which is confirmed by logs:However, the actual resulting connexion fails immediately with the following traceback (true sensitive values are edited out in all caps):
Which seems to indicate that the url provided by the server picker is not properly read or parsed.
Furthermore, manually registering the remote cluster using the
https://jh-cluster.mycompany.com/token?=MYTOKEN
functions perfectly well.Any idea what is going on? Thanks!
VS Code Version
1.76.2
Jupyter Extension Version
v2023.3.1000641008
Jupyter logs
The text was updated successfully, but these errors were encountered: