Extension fails to start on Linux.

[GlacierFox]

The installed extension fails to load for me at startup. Here's the error message in the language server output:

Language server powershell-es:

error while executing at wasm backtrace:
    0: 0x1306b - powershell.wasm!__rust_start_panic
    1: 0x11df4 - powershell.wasm!rust_panic
    2: 0x11dc7 - powershell.wasm!std::panicking::rust_panic_with_hook::h79071f5fb265d1d9
    3: 0x10d06 - powershell.wasm!std::panicking::begin_panic_handler::{{closure}}::h410c57f452410813
    4: 0x10c72 - powershell.wasm!std::sys::backtrace::__rust_end_short_backtrace::h514500abf2a2d0ca
    5: 0x1175b - powershell.wasm!rust_begin_unwind
    6: 0x18b3e - powershell.wasm!core::panicking::panic_fmt::he306018bf71f8e67
    7: 0x1a928 - powershell.wasm!core::result::unwrap_failed::h270adb30136b6536
    8: 0x3c08 - powershell.wasm!<powershell::PowerShellExtension as zed_extension_api::Extension>::language_server_command::h4b0c674e8101772d
    9: 0x4238 - powershell.wasm!zed_extension_api::wit::_export_language_server_command_cabi::h2a48dddd550bbbb8
   10: 0x85ce - powershell.wasm!language-server-command
   11: 0x1ce82 - powershell.wasm!language-server-command.command_export
-- stderr--

Zed Version: 0.198.3
Extension Version: 0.3.0
OS: Fedora

[steckes]

Yeah the error is a bit annoying, I just want to have the highlighting of the extension, it's fine if the rest doesn't work but I don't want to see this error all the time in the IDE...

[wingyplus]

I'm very busy at the moment. If anyone can tackle this issue, the PR is very welcome.

[Ctorum]

+1. It closes all the zed open windows as well.

[wearrrrr]

I noticed that it didn't crash if I installed it as a dev extension, which is as simple as cloning it and then opening the command palette and typing "dev extension", then selecting the folder you cloned.

I think that the extension that's on zed is either trying to do something more that causes a panic, or it's just outdated.

[MrSubidubi]

@wearrrrr This happens because on main, the error is fixed: #17

@wingyplus Could you perhaps release another version of this extension to the extension registry please?