-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wrong extensionKind for remote session #114
Comments
I've now been able to do more debugging on this. Owlbear is working on the base Windows setup, but not when working in Remote Windows for WSL or in the dev container. So that's an issue with either Remote Windows and Owlbear, or OS compatibility. Maybe this is going to be something simple like setting whether this extension runs in the host or client of a remote session. I'll test that when I can, but does anyone here already know whether Owlbear is compatible with Linux? Edit: from #108 I take it that Owlbear is better tested Unix platforms than windows. I'm guessing that this is a problem with remote access, then. This extension development doc will probably be useful on this ticket. The first thing to try would be to set the extension location in the package.json which lines up with my hunch that the wasm is getting loaded onto the wrong node interpreter. |
OK, I just used the |
Thanks for the thoughtful investigation here David, and for putting up a fix! I'll take a look at your PR this evening (EST) 🤘 |
Describe the bug
![image](https://private-user-images.githubusercontent.com/5530960/306682424-646c6da0-cc5e-4ec8-95f8-85bc1a2ee801.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEzMjkxMjEsIm5iZiI6MTcyMTMyODgyMSwicGF0aCI6Ii81NTMwOTYwLzMwNjY4MjQyNC02NDZjNmRhMC1jYzVlLTRlYzgtOTVmOC04NWJjMWEyZWU4MDEucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcxOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MThUMTg1MzQxWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YTE4N2NlOGIzZTZjOTc3MDExNzU2MzUzNWUxMWYzMWFjOTIyMDBlMjgxZTFjY2I4ZDk3MGFkZDllODAyMDQzYiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.UyIDpiIN-_f1qi-bqrt4ffzPaz9Kus3m5q7yxZYixt4)
All commands error out immediately after installing.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Commands execute without error and perform edits
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
when I run a command from a keystroke, that errors out too:
![image](https://private-user-images.githubusercontent.com/5530960/306684026-36d479fa-5ab7-4de5-a4dc-3667ff6a737e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEzMjkxMjEsIm5iZiI6MTcyMTMyODgyMSwicGF0aCI6Ii81NTMwOTYwLzMwNjY4NDAyNi0zNmQ0NzlmYS01YWI3LTRkZTUtYTRkYy0zNjY3ZmY2YTczN2UucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcxOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MThUMTg1MzQxWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZWFlMWI3MDQ0ZDJkMGFjNTdhMmEzZDcwMTRmMTZkMWI3NGM5ZGM1YTY3N2E2MzhmZGY2YmY4ODhlOGQzM2NlNyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.3haXQCLfO5g2wY2x2VorE4ufvy5Hcxg4QudPaRXxlsY)
I'm using a vscode remote setup with a WSL/Docker dev environment.
I refreshed the window but haven't done a cold start of vscode since installing.
The text was updated successfully, but these errors were encountered: