Python Project using existing venv won't start interpreter #5730
Assignees
Labels
area: core
Issues related to Core category.
area: runtimes
Issues related to Language Runtimes
regression
Milestone
Comments
jonvanausdeln
added
the
area: project wizard
|
Reminds me of: #5286 Some console output from a failed run: ERR Creating session for language runtime 991fdf617151cbb9d45a4e4c00c795a9 (language: Python name: Python 3.10.12 (Global) version: 3.10.12) failed. Reason: Error: Interpreter /bin/python3.10 (path: /bin/python3.10) not found in available Python interpreters:
DEBUG Error starting runtime session: Error: Interpreter /bin/python3.10 (path: /bin/python3.10) not found in available Python interpreters:
ERR Interpreter /bin/python3.10 (path: /bin/python3.10) not found in available Python interpreters: : Error: Interpreter /bin/python3.10 (path: /bin/python3.10) not found in available Python interpreters:
at new PythonRuntimeSession (/home/runner/work/positron/positron/extensions/positron-python/out/client/positron/session.js:72:19)
at PythonRuntimeManager.createSession (/home/runner/work/positron/positron/extensions/positron-python/out/client/positron/manager.js:144:16)
at async ExtHostLanguageRuntime.$createLanguageRuntimeSession (/home/runner/work/positron/positron/out/vs/workbench/api/common/positron/extHostLanguageRuntime.js:82:33)
|
|
This could have the same root cause as #5718? |
|
This also repros locally. This is from the debug console |
jonvanausdeln
added a commit
that referenced
this issue
Dec 14, 2024
Due to #5730 need to skip the ipykernel new project tests. ### QA Notes Clean CI runs <!-- Add additional information for QA on how to validate the change, paying special attention to the level of risk, adjacent areas that could be affected by the change, and any important contextual information not present in the linked issues. -->
juliasilge
added
area: core
seeM
added a commit
that referenced
this issue
Dec 19, 2024
Attempts to address #5730. My hunch is that `getInterpreters()` doesn't wait for the Python extension to complete its discovery process, so it's possible to get there before our runtime's interpreter is discovered. The whole point of restoring a workspace-affiliated runtime is to skip discovery. It looks like `getInterpreterDetails()` is a better fit, since (I think) it "resolves" an interpreter path to a `PythonEnvironment` independent of discovery. ### QA Notes E2E tests C609619 and C609617 should pass in CI: * Passing E2E run: https://github.com/posit-dev/positron/actions/runs/12387951151/job/34578222238 * 10x run of both failing tests: https://d38p2avprg8il3.cloudfront.net/playwright-report-12389107722-6803/index.html. There was a single failure, but that looks like an unrelated issue. Python and Reticulate runtimes should continue to function as expected.
jonvanausdeln
added a commit
that referenced
this issue
Dec 20, 2024
<!-- Thank you for submitting a pull request. If this is your first pull request you can find information about contributing here: * https://github.com/posit-dev/positron/blob/main/CONTRIBUTING.md We recommend synchronizing your branch with the latest changes in the main branch by either pulling or rebasing. --> <!-- Describe briefly what problem this pull request resolves, or what new feature it introduces. Include screenshots of any new or altered UI. Link to any GitHub issues but avoid "magic" keywords that will automatically close the issue. If there are any details about your approach that are unintuitive or you want to draw attention to, please describe them here. --> ### Intent These tests were turned back on, but need to still be skipped due to #5730 ### QA Notes Windows CI should now pass <!-- Add additional information for QA on how to validate the change, paying special attention to the level of risk, adjacent areas that could be affected by the change, and any important contextual information not present in the linked issues. -->
Verified FixedPositron Version(s) : 2025.01.0-141 Test scenario(s)venv now starts as expected. There seem to still be something causing some CI failures, but don't seem to be related to this issue. I'm investigating that separately. Link(s) to TestRail test cases run or created: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System details:
Positron and OS details:
Interpreter details:
Python 3.10.10 (but version doesn't matter)
Describe the issue:
The interpreter doesn't start in a new project when selecting an existing venv. nor when opening an existing project with a venv.
This is seen in our automated New Project with ipykernel installed test. causing it to fail.
Steps to reproduce the issue:
Note that the interpreter doesn't start up. However you can manually start the interpreter. It used to auto start the interpreter. This is causing our test to fail.
Expected or desired behavior:
Console interpreter starts up automatically
Were there any error messages in the UI, Output panel, or Developer Tools console?
QA NOTES
Two tests skipped will need to be turned back on when resolved. See #5731
The text was updated successfully, but these errors were encountered: