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

"Debug and Run" Button doesn't recognize predefined interpreter in settings.json and selects a different one #6835

Closed
2 tasks done
atheo89 opened this issue Jun 12, 2024 · 3 comments
Labels
bug Something isn't working triage This issue needs to be triaged by a maintainer

Comments

@atheo89
Copy link

atheo89 commented Jun 12, 2024

Is there an existing issue for this?

  • I have searched the existing issues

OS/Web Information

  • Web Browser: Chrome/firefox
  • Local OS: fedora
  • Remote OS: fedora
  • Remote Architecture: amd64
  • code-server --version: 4.22.0
  • ms python: v2024.2.1

Steps to Reproduce

  1. Launch code server
  2. Install ms-python extension
  3. Set on settings.json your preferred interpreter "python.defaultInterpreterPath": "/path/to/different/interpreter"
  4. Reload Window
  5. Create a test python file
  6. Press Run > icon on the top right. It will run your file without issue using the predefined interpreter.
  7. Now press on Run and Debug and see on the bottom right banner the in the python section use a different interpreter from the one that we pre defined.

Expected

The "Run and Debug" button to use the python interpreter that is been defined on the settings.json file by the user.

Actual

"Debug and Run" Button doesn't recognize predefined interpreter in settings.json and selects a different one, in contrary the Run icon on top left on the screen works as expected.

Logs

No response

Screenshot/Video

No response

Does this bug reproduce in native VS Code?

I did not test native VS Code

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?

  • I am using a secure context.

Notes

No response

@atheo89 atheo89 added bug Something isn't working triage This issue needs to be triaged by a maintainer labels Jun 12, 2024
@code-asher
Copy link
Member

I would guess this needs to be filed with the extension, but we should test VS Code and Codespaces to make sure it is not somehow a problem in code-server.

@atheo89
Copy link
Author

atheo89 commented Jun 20, 2024

Thank you for your reply @code-asher!
I thought the same later on and i opened a question on python extension repo. microsoft/vscode-python-debugger#363

@code-asher
Copy link
Member

I will close this for now since I think there is nothing we can fix on code-server's side, but we can reopen if that changes.

@code-asher code-asher closed this as not planned Won't fix, can't repro, duplicate, stale Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage This issue needs to be triaged by a maintainer
Projects
None yet
Development

No branches or pull requests

2 participants