Skip to content

launching a local integrated terminal from wsl will look for linux location for venv #1027

Closed as not planned
Closed as not planned
launching a local integrated terminal from wsl will look for linux location for venv#1027
Assignees
edvilmeanthonykim1
Labels
area-activationIssue related to activation. Root cause can be from interpreter selection or activation in terminalarea-terminalEnvironment extension specific terminal issues.bugIssue identified by VS Code Team member as probable buginfo-neededIssue requires more information from postertriage-needed

Description

@amunger
Aaron Munger (amunger)
opened on Dec 4, 2025
Image

it looks like it's trying to run a script from WSL in the local pwsh terminal

Activity

  1. Aaron Munger (amunger)
    assigned
    Anthony Kim (anthonykim1)
    on Dec 4, 2025
  2. github-actions
    added
    triage-needed
    on Dec 4, 2025
  3. github-actions
    unassigned
    Anthony Kim (anthonykim1)
    on Dec 4, 2025
  4. Anthony Kim (anthonykim1)
    self-assigned this
    on Dec 4, 2025
  5. Anthony Kim (anthonykim1)
    removed
    triage-needed
    on Dec 4, 2025
  6. Eleanor Boyd (eleanorjboyd)
    added
    bugIssue identified by VS Code Team member as probable bug
    on Dec 8, 2025

  7. eleanorjboyd commented on Feb 18, 2026

    @eleanorjboyd
    Eleanor Boyd (eleanorjboyd)
    on Feb 18, 2026
    Member

    Aaron are you able to try this with the newest release version of the extension and let me know if it works?

  8. amunger commented on Feb 23, 2026

    @amunger
    Aaron Munger (amunger)
    on Feb 23, 2026
    ContributorAuthor

    yes still repros for me

  9. anthonykim1 commented on Mar 5, 2026

    @anthonykim1
    Anthony Kim (anthonykim1)
    on Mar 5, 2026
    Contributor

    Ah, this is a great edge case. I'll look into how we can fix this

  10. Anthony Kim (anthonykim1)
    added
    area-terminalEnvironment extension specific terminal issues.
    area-activationIssue related to activation. Root cause can be from interpreter selection or activation in terminal
    on Mar 5, 2026
  11. Anthony Kim (anthonykim1)
    added this to the 1.112.0 milestone on Mar 5, 2026
  12. Anthony Kim (anthonykim1)
    modified the milestones: 1.112.0, on Mar 14, 2026

  13. 6 remaining items

  14. Anthony Kim (anthonykim1)
    added this to the 1.115.0 milestone on Mar 30, 2026
  15. Anthony Kim (anthonykim1)
    modified the milestones: 1.115.0, 1.116.0 on Apr 6, 2026
  16. Alex Ross (alexr00)
    removed this from the 1.116.0 milestone on Apr 13, 2026
  17. Eleanor Boyd (eleanorjboyd)
    added a commit that references this issue on Apr 22, 2026

    Add GitHub issue templates (Bug Report, Feature Request, Question) (#…

    ee40206
  18. Stella Huang (StellaHuang95)
    added a commit that references this issue on Apr 30, 2026

    Add GitHub issue templates (Bug Report, Feature Request, Question) (m…

    620fb1c
  19. Eleanor Boyd (eleanorjboyd)
    added
    info-neededIssue requires more information from poster
    on Sep 24, 2026

  20. eleanorjboyd commented on Sep 24, 2026

    @eleanorjboyd
    Eleanor Boyd (eleanorjboyd)
    on Sep 24, 2026
    Member

    Anthony Kim (@anthonykim1) can you give some info on how we can investigate / fix this ?

  21. Eleanor Boyd (eleanorjboyd)
    added
    triage-needed
    and removed
    info-neededIssue requires more information from poster
    on Sep 30, 2026

  22. anthonykim1 commented on Oct 1, 2026

    @anthonykim1
    Anthony Kim (anthonykim1)
    on Oct 1, 2026
    Contributor

    There's probably way in core to get remote related info, and there's probably way somewhere to figure out whether particular launched terminal is local/remote. We'd need to ensure that when user opens local terminal we get/use activation info for that instead of for remote.

  23. github-actions
    added
    info-neededIssue requires more information from poster
    on Oct 1, 2026
  24. Anthony Kim (anthonykim1)
    assigned
    Eduardo Villalpando Mello (edvilme)
    on Oct 1, 2026

  25. github-actions commented on Oct 9, 2026

    @github-actions
    github-actionsbot
    on Oct 9, 2026 – with GitHub Actions

    Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

    Happy Coding!

  26. github-actions
    closed this as not plannedon Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area-activationIssue related to activation. Root cause can be from interpreter selection or activation in terminalarea-terminalEnvironment extension specific terminal issues.bugIssue identified by VS Code Team member as probable buginfo-neededIssue requires more information from postertriage-needed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions