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

Using an email address as a username fails to get a list of kernels #41

Closed
mastercard-rob opened this issue Oct 24, 2023 · 5 comments
Closed
Assignees
Labels
duplicate This issue or pull request already exists *duplicate Issue identified as a duplicate of another issue(s)

Comments

@mastercard-rob
Copy link

I have JupyterHub integrated with azuread and using email address as the username. The '@' is getting encoded and the call to /api/kernels is failing with a 404.

@DonJayamanne
Copy link
Collaborator

DonJayamanne commented Oct 24, 2023

Sorry you are running into this issue

Please can you try installing the latest pre-release version of the Jupyter hub extension
This was fixed in the pre release version

@marcelgs
Copy link

@mastercard-rob
I had to install the pre-release version (v2023.10.1003011100) of the Jupyter extension as well in order to get this to work.

@DonJayamanne
Copy link
Collaborator

Thanks closing as fixed

@dschach99
Copy link

I am currently running into a similar problem when using a username including brackets and whitespaces. The brackets '(' and ')' are getting encoded and the call also fails with a 404. Also, using the current pre-release version (v2023.10.1003492320) did not fix it.

@quantum-byte
Copy link

I am currently running into a similar problem when using a username including brackets and whitespaces. The brackets '(' and ')' are getting encoded and the call also fails with a 404. Also, using the current pre-release version (v2023.10.1003492320) did not fix it.

This is pretty sure not an issue in vscode-jupyter-hub but rather the vscode-jupyter extension. Please see #53

@DonJayamanne DonJayamanne added duplicate This issue or pull request already exists *duplicate Issue identified as a duplicate of another issue(s) labels Apr 2, 2024
@DonJayamanne DonJayamanne self-assigned this Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

5 participants