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

Non ZMQ doesn't work #10940

Closed
rchiodo opened this issue Jul 26, 2022 · 4 comments · Fixed by #10944
Closed

Non ZMQ doesn't work #10940

rchiodo opened this issue Jul 26, 2022 · 4 comments · Fixed by #10944
Labels
bug Issue identified by VS Code Team member as probable bug triage-needed Issue needs to be triaged

Comments

@rchiodo
Copy link
Contributor

rchiodo commented Jul 26, 2022

Not sure what the problem is, but if I go backwards to version 1002021048 everything works fine.

One of the changes on here is causing non ZMQ to break for me:
https://dev.azure.com/monacotools/Monaco/_traceability/runview/changes?currentRunId=178730

@rchiodo rchiodo added the bug Issue identified by VS Code Team member as probable bug label Jul 26, 2022
@github-actions github-actions bot added the triage-needed Issue needs to be triaged label Jul 26, 2022
@rchiodo
Copy link
Contributor Author

rchiodo commented Jul 26, 2022

Jupyter never responds to the waitForIdle.

@rchiodo
Copy link
Contributor Author

rchiodo commented Jul 26, 2022

This commit causes the error:
7308db8

@rchiodo
Copy link
Contributor Author

rchiodo commented Jul 26, 2022

Looking at the difference in how things are launched, with the newer change, the PATH environment variable is cased differently.

Here's a working kernelspec (from previous commit):

working.txt

Here's one that doesn't (generated with commit id: 7308db8)
bad.txt

Not sure if this is the root cause or not yet, but it's at least a difference.

@rchiodo
Copy link
Contributor Author

rchiodo commented Jul 26, 2022

Casing seems to be the root of the problem. Not sure how but that fixes it for me.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug triage-needed Issue needs to be triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant