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

Kernel Supervisor: Show environment when language runtime fails to start #579

Open
jmcphers opened this issue May 16, 2023 · 1 comment
Open
Labels
area: core Issues related to Core category. area: kallichore Issues related to the new kernel supervisor

Comments

@jmcphers
Copy link
Collaborator

Currently, we show the terminal output from a language runtime that fails to start, like this.

image

However, every single time I have tried to debug a startup failure, I have wanted to know what the environment variables were set to when the kernel was launched (as well as the exact launch command), and have wound up hacking print statements into kernel-wrapper.sh so I can see them. We should log these somewhere so that they can be brought up for debugging.

They don't need to be front-and-center, since showing all the environment variables at once creates a wall of text that makes the actual startup error hard to find, but they should be accessible somewhere.

@petetronic
Copy link
Collaborator

This will be useful for debugging customer issues. We should include it in the release.

@wesm wesm added the area: core Issues related to Core category. label Feb 29, 2024
@jmcphers jmcphers added the area: kallichore Issues related to the new kernel supervisor label Nov 21, 2024
@jmcphers jmcphers changed the title jupyter-adapter: Show environment when language runtime fails to start Kernel Supervisor: Show environment when language runtime fails to start Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues related to Core category. area: kallichore Issues related to the new kernel supervisor
Projects
None yet
Development

No branches or pull requests

3 participants