Skip to content

Update pathspecs in dev docs #41508

Closed
Closed

Description

@tega-ajise

Windows Version

Microsoft Windows [Version 10.0.26100.9106

WSL Version

2.7.12.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

Expected Behavior

The paths should be src/windows/service/exe/WslCoreVm.cpp, and src/windows/service/exe/WslCoreVm.cpp respectively. The source files are now in the "exe" folder

Actual Behavior

  • The path of the WslCoreVm implementation was src/windows/service/WslCoreVm.cpp
  • The path of the WSLCoreInstance was src/windows/service/WslCoreInstance.cpp
  • Both missing the "exe" folder

Diagnostic Logs

No response

Activity

  1. github-actions commented on Sep 3, 2026

    @github-actions
    Contributor

    Logs are required for review from WSL team

    If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
    Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

    How to collect WSL logs

    Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

    Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
    Set-ExecutionPolicy Bypass -Scope Process -Force
    .\collect-wsl-logs.ps1
    

    The script will output the path of the log file once done.

    If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

    Once completed please upload the output files to this GitHub issue.

    See Collect WSL logs (recommended method).

    If you choose to email these logs instead of attaching them to the bug, please send them to [email protected] with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

  2. tega-ajise commented on Sep 3, 2026

    @tega-ajise
    ContributorAuthor

    /feature

  3. github-actions commented on Sep 3, 2026

    @github-actions
    Contributor
    Diagnostic information
    Found '/feature', adding tag 'feature'
    
  4. tega-ajise commented on Sep 3, 2026

    @tega-ajise
    ContributorAuthor

    This should be a quick win, just to help with a very small aspect of understanding the technical details

  5. OneBlue commented on Sep 15, 2026

    @OneBlue
    Collaborator

    Closing since the doc issue has been resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions