Replies: 2 comments
-
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt: The script will output the path of the log file once done. If this is a networking issue, please use 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 wsl-gh-logs@microsoft.com 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'. |
Beta Was this translation helpful? Give feedback.
-
|
Some kind of thoughts around this from maintainers? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am going out on a limb here, but I feel it needs to get pointed out.
Why does the top voted issues not get some kind of priority? Is there a product owner here that feel they are not worth investigating? Take a look at the picture below. Most issues are 8 years old. It is an insanely long time to not work on any of those issues.
These issues are all limiting the WSL experience in various ways. Important ways to most. Many users are frustrated with the close-to-zero lack of activity by WSL developers in these issues. It feels like something is broken in the WoW for WSL issues. Even great editors like Zed has made custom workarounds.
WSL is amazing. I think we all just wished prioritization worked partially on top-rated issues by the user base.
Beta Was this translation helpful? Give feedback.
All reactions