-
Notifications
You must be signed in to change notification settings - Fork 286
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
kernel_actions/v1 spec expects field that is not available #1299
Comments
This condition is not exclusive to the use of a gateway - correct? Any failure of a kernel's start will not (necessarily) have a kernel_id present and, as a result, violate the event schema's validation. I just want to make sure my understanding is correct and it's just less common for local start failures to occur (although it could be easily simulated by, for example, invalidating the |
Yes, that's correct . |
Solved by #1300 |
The new release version is `0.0.4`. This also updates the `jupyter-server` dependency to `>=2.7.3`. That is so users pick up the fix for [this issue](jupyter-server/jupyter_server#1299)
Description
When Enterprise Gateway fails to create a kernel for the jupyter notebook, the response is not expected to contain any kernel ID. However, the kernel_actions/v1.yaml expects that kernel_id be present. The error response results in subsequent event validation error due to kernel_id that is set to None.
Reproduce
Expected behavior
When the Gateway fails to launch kernel it should also log that as an event
Context
Troubleshoot Output
Command Line Output
Browser Output
The text was updated successfully, but these errors were encountered: