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

Extension API getActiveInterperter and getInterpreters return undefined and [] #17303

Closed
DonJayamanne opened this issue Sep 7, 2021 · 1 comment
Assignees
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster investigating We are looking into the cause of the issue partner ask regression Bug didn't exist in a previous release

Comments

@DonJayamanne
Copy link

DonJayamanne commented Sep 7, 2021

Environment data

  • VS Code version: 1.6.0
  • Extension version (available under the Extensions sidebar): Latest Marketplace
  • OS and version: Ubuntu 20 (CI)
  • Python version (& distribution if applicable, e.g. Anaconda): 3.8.11
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
  • Relevant/affected Python packages and their versions: Global
  • Relevant/affected Python-related VS Code extensions and their versions: N/A
  • Value of the python.languageServer setting: n/a

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]

Expected behaviour

getActiveInterperter and getInterpreters should not return empty values

Actual behaviour

On CI, the above two methods return empty values.
Our tests have been failing since thursday. I believe after the new Python extension was released.
We didn't chage any of the code in jupyter extension.

I can see from our logs the first calls to getActiveInterpreter & getInterpreters always returns undefined and []
this is causing our CI tests to fail & I expect this will will cause issues on end user machines as well.

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

Very difficult to repro on the client side (i guess its a timing thing)
This fails very consistently on CI, See last few runs of the PR microsoft/vscode-jupyter#7410 (last few runs)
The first calls to the two methods always return

Logs

See last few runs of the PR microsoft/vscode-jupyter#7410 (last few runs)

See here https://pipelines.actions.githubusercontent.com/KyBlh4sBTj8eoTzBTvt0CAApvyyj3PXuc4Tbg2yHyMGda4Kk7D/_apis/pipelines/1/runs/17104/signedlogcontent/7?urlExpires=2021-09-07T18%3A05%3A55.8149811Z&urlSigningMethod=HMACV1&urlSignature=%2F2YZdnccCib3FsH92LNpDZid6Mr7dPi9RQy7n%2BamSu0%3D

All outputs from the PR microsoft/vscode-jupyter#7410

@DonJayamanne DonJayamanne added bug Issue identified by VS Code Team member as probable bug triage-needed Needs assignment to the proper sub-team labels Sep 7, 2021
@DonJayamanne DonJayamanne changed the title Regression in Extension API getActiveInterperter and getInterpreters return undefined and [] Extension API getActiveInterperter and getInterpreters return undefined and [] Sep 7, 2021
@karthiknadig karthiknadig added P0 partner ask area-environments Features relating to handling interpreter environments regression Bug didn't exist in a previous release and removed triage-needed Needs assignment to the proper sub-team labels Sep 7, 2021
@karrtikr karrtikr added needs PR and removed triage labels Sep 7, 2021
@karthiknadig karthiknadig added this to the August Recovery milestone Sep 8, 2021
@karrtikr
Copy link

@DonJayamanne This should now be fixed with the latest release of the extension (when not in discovery exp), can you try?

@karrtikr karrtikr added info-needed Issue requires more information from poster investigating We are looking into the cause of the issue needs PR and removed needs PR labels Sep 13, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster investigating We are looking into the cause of the issue partner ask regression Bug didn't exist in a previous release
Projects
None yet
Development

No branches or pull requests

3 participants