Extension Doesn't Start on WSL Ubuntu
lyao6104 opened this issue · 4 comments
I'm using version 2.2.0 of the extension, and when I open an Elm project in WSL the extension doesn't start at all, and I couldn't find any related messages in the output log either.
Expected Behavior
The extension starts when an elm.json file is found, as the changelog says.
Current Behavior
When an Elm project is opened in WSL, the extension doesn't start at all, even with the elm-spa-example. I tried rolling back to 2.1.0, as well as opening the project in regular Windows (separately), and in these cases, the issue did not occur (i.e. the extension worked properly).
Possible Solution
I'm not sure what a possible solution would be, but this line in the 2.2.0 changelog
Start extension, if an elm.json is found, not on entering an elm file
might be related.
Steps to Reproduce (for bugs)
- In WSL Ubuntu, navigate to the directory of an Elm project.
- Start VS Code using
code . - VS Code launches, but the Elm extension doesn't start, even in a valid Elm project.
Your Environment
- Version used: 2.2.0
- Editor name and version (e.g. VSCode 1.36.1): VSCode 1.58.0
- Environment name and version (e.g. node.js 5.4): node.js 14.17.0
- Operating System and version: Ubuntu 18.04.5 LTS running on WSL2
I can confirm behaviour on WSL with Debian GNU/Linux 10 (buster) even with an elm.json on version 2.2.0. Version 2.1.0 starts up perfectly. Nothing in the logs that I could find.
VSCode details:
Version: 1.58.0 (user setup)
Commit: 2d23c42a936db1c7b3b06f918cde29561cc47cd6
Date: 2021-07-08T06:54:55.083Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows_NT x64 10.0.19043
Can you setup an environment and debug this, like it's explained in the readme? It might indeed be the matching of elm.json that's not working in wsl. But I don't have a windows to test this.
I can't speak for sumo, but this issue seems to have been resolved for me in 2.2.1.
Closing for now. Feel free to reach out and reopen this.