Environment extension shows wrong setting value for activation in wsl #894

Activity

1. github-actions

   added

   triage-needed

   on Oct 4, 2025
2. karthiknadig commented on Oct 4, 2025

   

   Karthik Nadig (karthiknadig)

   on Oct 4, 2025

   Member

   More actions

   WSL has 3 layers of settings User, Remote and workspace. Since wow support the activation setting at machine level only, there are two possible locations user and remote. Remote takes precedence over user.
3. anthonykim1 commented on Oct 6, 2025

   

   Anthony Kim (anthonykim1)

   on Oct 6, 2025

   Last edited by anthonykim1

   ContributorAuthor

   More actions

   GlobalRemoteValue is undefined:

   Maybe since its machine level , the remote setting doesnt get picked up.
4. eleanorjboyd commented on Oct 6, 2025

   

   Eleanor Boyd (eleanorjboyd)

   on Oct 6, 2025

   Contributor

   More actions

   Karthik Nadig (@karthiknadig) would we want to scope this to window for remote scenarios? Since its scoped to machine right now I don't thinkkk it will then work in this remote case.
5. github-actions

   added

   info-neededIssue requires more information from posterIssue requires more information from poster

   on Oct 6, 2025
6. Eleanor Boyd (eleanorjboyd)

   self-assigned this

   on Oct 6, 2025
7. Eleanor Boyd (eleanorjboyd)

   closed this as completedin #897on Oct 7, 2025
8. pull

   added a commit that references this issue on Oct 7, 2025

   Fix bug with getAutoActivationType (microsoft#897)

   ...

   8869aff
9. Eleanor Boyd (eleanorjboyd)

   added a commit that references this issue on Oct 8, 2025

   Fix bug with getAutoActivationType (microsoft#897)

   ...

   91ead9e
10. NgCuong (NguyenCuong1989)

    added a commit that references this issue on Oct 23, 2025

    Fix bug with getAutoActivationType (#897)

    ...

    fa90963
11. github-actions

    locked as resolved and limited conversation to collaborators on Apr 30, 2026