-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
getActiveEnvironmentPath & resolveEnvironment fails to return the active environment information #20147
Comments
Note: If you look at the logs, further below the information for the same interpreter is actually successfully returned
from the Windows job https://github.com/microsoft/vscode-jupyter/actions/runs/3382377101/jobs/5617238307 Looks like the I think the fact that it returns partial information & sometimes |
I guess I have the same issue. When I try to use pytest from the extension I got an error at the Output > Python window:
|
I don't see a way to access Jupyter logs in the above run. |
@sevvalmehder Your issue seems different, please open a new issue with the logs. |
I cannot reproduce this on Windows CI Python 3.10 (#20166): https://github.com/microsoft/vscode-python/actions/runs/3409251206/jobs/5670784030 I've made some tweaks in #20165 which could potentially help, and added more logging. Would need logs from Jupyter or a minimal extension reproducing this before I can proceed further. |
expand the test run failure which takes around 1.5 minutes and you'll see all of the logs
all our ci things contains verbose logs, hence you should have access to all the logs there |
Here are the logs, under this section Same error, the return value from Python seems incorect
You can get the logs from the latest run here https://github.com/microsoft/vscode-jupyter/actions/runs/3408919625/jobs/5670063769 As you can see the return value we're getting contains empty values for Can I suggest you add some verbose logging in Python extension so you can see what's being sent back to the Jupyter extension,
Not sure what's not going on there, but this is pretty consistently failing in our CI now.
Thanks, let me know if you need additional logs or the like. |
Ah, I can't find the Python logs, can you help with where to find it in the GHA run? |
|
Based on the logs here, sometimes Python extension returns https://pipelines.actions.githubusercontent.com/serviceHosts/e2216a9b-4bf5-4e67-aba3-9767e42c612e/_apis/pipelines/1/runs/49154/signedlogcontent/19?urlExpires=2022-11-07T22%3A01%3A13.1720408Z&urlSigningMethod=HMACV1&urlSignature=r5fqaGZVrroe216DJatfXs8zlnUFR6a6RJ4DA1IwlxA%3D
|
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
@DonJayamanne how is that fixing this issue? I'm still working on this some parts have been fixed. |
It should fix the other issue though: #20176. |
Verified that both the issues are now fixed in microsoft/vscode-jupyter#11936. |
I've run into this issue a few times on our Windows CI, basically the activeInterpreter is
undefined
Here's the code
& here's the output from our CI
Here are the logs from the Python extension
I guess the most interesting part is
Error: python -c "import sys;print(sys.executable)" resulted in empty stdout
Click me
The text was updated successfully, but these errors were encountered: