-
Notifications
You must be signed in to change notification settings - Fork 29
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
Running the custom kernel example - error when starting kernel from JupyterLab #57
Comments
Can you please show the image tag of the gateway and kernel? |
Hello, could I know whether you solve this problem? I meet the same issue, I check the version of jupyter_client is 7.1.0. Could changing the version of jupyter_client work? I try to deploy with enterprise-gateway alone instead of elastic-jupyter-operator, that works. I'll appreciate it if you could help. |
Hello, Mr. Gao. I meet the same question. I try the demo as quick-start but it doesn't work. The tags of my gateway and kernel are both 2.6.0. I want to know whether some version conflict exists. I have tried deploying only with enterprise-gateway and it works. I am interested in what kind of differences between your images and theirs. I am sorry I cannot access your image information and I do not obtain the answer in your code. I'll appreciate it if you could help. |
OK I will verify it today. |
@ycsong1212 Did you follow the guide here? https://github.com/skai-x/elastic-jupyter-operator/tree/master/docs#remote-kernels Remote kernel or Remote kernels with custom configuration |
I think I do. First I apply crds by prepare.yaml and then make deploy. I tried elastic-with-custom-kernels demo. I apply four crds under examples/elastic-with-custom-kernels directory. Then I port-forward my notebook pod. When I launch kernel, kernel error occurs. Such error is reported in gateway container. |
I have same error, how can i fix it? |
gateway log error message: [I 220707 10:14:18 web:2239] 200 GET /api/kernels (10.244.2.XX) 6.00ms [E 2022-07-07 10:14:46.063 EnterpriseGatewayApp] init() got an unexpected keyword argument 'kernel_id' |
I did not reproduce it before. I will take a look ASAP but not sure if I can reproduce this time. |
It looks like a version problem related to enterprise gateway. |
@gaocegege Let's try to fix the issue |
This repo is not maintained? |
The org and repository belong to Tencent Cloud. And I am not sure if there is actively maintained. |
I encountered the same issue, have you resolved it? |
When going through the custom kernel example everything starts correctly in k8s, but when starting the kernel from the notebook it produced a 500 HTTP error:
Seems like the error is some version incompatibility with enterprise gateway. Here are the logs from the gateway:
Error:
TypeError: __init__() got an unexpected keyword argument 'kernel_id'
This seems related to this issue: jupyter-server/enterprise_gateway#1024
Seems like it's using
jupyter-client 7.1.0
, which might be the problem? I'll try to confirmThe text was updated successfully, but these errors were encountered: