Skip to content
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

an error occurs after installing RustOwl #28

Open
vremyavnikuda opened this issue Feb 16, 2025 · 5 comments
Open

an error occurs after installing RustOwl #28

vremyavnikuda opened this issue Feb 16, 2025 · 5 comments
Labels
bug Something isn't working

Comments

@vremyavnikuda
Copy link

thread 'LspServer' panicked at crates\rust-analyzer\src\main_loop.rs:764:84:
called `Result::unwrap()` on an `Err` value: Error { kind: NotFound, message: "program not found" }
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/std\src\panicking.rs:665
   1: core::panicking::panic_fmt
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/core\src\panicking.rs:76
   2: core::result::unwrap_failed
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/core\src\result.rs:1699
   3: <rust_analyzer::main_loop::Event as core::fmt::Debug>::fmt
   4: <rust_analyzer::main_loop::Event as core::fmt::Debug>::fmt
   5: rust_analyzer::main_loop::main_loop
   6: rust_analyzer::run_server
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread 'main' panicked at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\jod-thread-0.1.2\src\lib.rs:33:22:
called `Result::unwrap()` on an `Err` value: Any { .. }
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/std\src\panicking.rs:665
   1: core::panicking::panic_fmt
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/core\src\panicking.rs:76
   2: core::result::unwrap_failed
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/core\src\result.rs:1699
   3: jod_thread::JoinHandle<T>::join
   4: <tracing_subscriber::fmt::format::Writer as core::fmt::Write>::write_str
   5: <tracing_subscriber::fmt::format::Writer as core::fmt::Write>::write_str
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[Info  - 13:01:46] Connection to server got closed. Server will restart.
true
[Error - 13:01:46] Server process exited with code 101.
thread 'LspServer' panicked at crates\rust-analyzer\src\main_loop.rs:764:84:
called `Result::unwrap()` on an `Err` value: Error { kind: NotFound, message: "program not found" }
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/std\src\panicking.rs:665
   1: core::panicking::panic_fmt
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/core\src\panicking.rs:76
   2: core::result::unwrap_failed
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/core\src\result.rs:1699
   3: <rust_analyzer::main_loop::Event as core::fmt::Debug>::fmt
   4: <rust_analyzer::main_loop::Event as core::fmt::Debug>::fmt
   5: rust_analyzer::main_loop::main_loop
   6: rust_analyzer::run_server
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread 'main' panicked at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\jod-thread-0.1.2\src\lib.rs:33:22:
called `Result::unwrap()` on an `Err` value: Any { .. }
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/std\src\panicking.rs:665
   1: core::panicking::panic_fmt
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/core\src\panicking.rs:76
   2: core::result::unwrap_failed
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/core\src\result.rs:1699
   3: jod_thread::JoinHandle<T>::join
   4: <tracing_subscriber::fmt::format::Writer as core::fmt::Write>::write_str
   5: <tracing_subscriber::fmt::format::Writer as core::fmt::Write>::write_str
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[Error - 13:01:47] Server process exited with code 101.
[Error - 13:01:47] Client Rust Analyzer Language Server: connection to server is erroring.
Cannot call write after a stream was destroyed
[Error - 13:01:47] Request textDocument/diagnostic failed.
  Message: Cannot call write after a stream was destroyed
  Code: -32099 
[Error - 13:01:47] Document pull failed for text document file:///c%3A/repository/codewars/rust/task/src/main.rs
  Message: Cannot call write after a stream was destroyed
  Code: -32099 
[Info  - 13:01:47] Connection to server got closed. Server will restart.
true
thread 'LspServer' panicked at crates\rust-analyzer\src\main_loop.rs:764:84:
called `Result::unwrap()` on an `Err` value: Error { kind: NotFound, message: "program not found" }
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/std\src\panicking.rs:665
   1: core::panicking::panic_fmt
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/core\src\panicking.rs:76
   2: core::result::unwrap_failed
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/core\src\result.rs:1699
   3: <rust_analyzer::main_loop::Event as core::fmt::Debug>::fmt
   4: <rust_analyzer::main_loop::Event as core::fmt::Debug>::fmt
   5: rust_analyzer::main_loop::main_loop
   6: rust_analyzer::run_server
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread 'main' panicked at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\jod-thread-0.1.2\src\lib.rs:33:22:
called `Result::unwrap()` on an `Err` value: Any { .. }
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/std\src\panicking.rs:665
   1: core::panicking::panic_fmt
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/core\src\panicking.rs:76
   2: core::result::unwrap_failed
             at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58\library/core\src\result.rs:1699
   3: jod_thread::JoinHandle<T>::join
   4: <tracing_subscriber::fmt::format::Writer as core::fmt::Write>::write_str
   5: <tracing_subscriber::fmt::format::Writer as core::fmt::Write>::write_str
[Error - 13:01:49] Client Rust Analyzer Language Server: connection to server is erroring.
write EPIPE
Shutting down server.
[Error - 13:01:49] Request textDocument/documentSymbol failed.
  Message: write EPIPE
  Code: -32099 
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[Error - 13:01:49] Client Rust Analyzer Language Server: connection to server is erroring.
Cannot call write after a stream was destroyed
[Error - 13:01:49] Client Rust Analyzer Language Server: connection to server is erroring.
Cannot call write after a stream was destroyed
[Error - 13:01:49] Request textDocument/inlayHint failed.
  Message: Cannot call write after a stream was destroyed
  Code: -32099 
[Error - 13:01:49] Connection to server got closed. Server will not be restarted.
[Error - 13:01:49] Server process exited with code 101.
[Error - 13:01:49] Stopping server failed
  Message: Cannot call write after a stream was destroyed
  Code: -32099 
[Error - 13:01:49] Stopping server failed
  Message: Cannot call write after a stream was destroyed
  Code: -32099 

info

rustup -V
rustup 1.27.1 (54dd3d00f 2024-04-24)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.84.1 (e71f9a9a9 2025-01-27)`

Windows 11 Pro
24H2
26120.3073
@cordx56
Copy link
Owner

cordx56 commented Feb 16, 2025

Thanks for your report.
Please tell me what editor do you use. And also, please check whether rust-analyzer works without RustOwl (The error messages seems to from rust-analyzer)

@cordx56 cordx56 added the bug Something isn't working label Feb 16, 2025
@vremyavnikuda
Copy link
Author

it will take me a little longer than I expected to gather more information.

it was possible to restore the functionality of rust-analyzer using complex methods. i manually deleted the {USERNAME}\.cargo\bin

cargo-owl.exe
cargo-owlsp.exe
rustowlc.exe

reinstalled rustup
reinstalled vscode

but I'm sure there are less drastic ways.

i have several ways in mind, i want to try them.

@cordx56
Copy link
Owner

cordx56 commented Feb 16, 2025

We sincerely apologize for the inconvenience.

@vremyavnikuda
Copy link
Author

vremyavnikuda commented Feb 16, 2025

We sincerely apologize for the inconvenience.

I don't think it's your fault here, most likely I was
able to fix something in the settings for

Windows 11 Pro
24H2
26120.3073

rustc -V
rustc 1.84.1 (e71f9a9a9 2025-01-27)
rustup -V
rustup 1.27.1 (54dd3d00f 2024-04-24)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.84.1 (e71f9a9a9 2025-01-27)`

to do this, the installation was performed via git bash
curl -L"https://github.com/cordx56/rustowl/releases/download/v0.1.1/install.sh " | sh
vscode version

Version: 1.97.2 (user setup)
Commit: e54c774e0add60467559eb0d1e229c6452cf8447
Date: 2025-02-12T23:20:35.343Z
Electron: 32.2.7
ElectronBuildId: 10982180
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.26120

the rust-analyzer settings should not be involved in settings.json

I'm trying to reproduce the error.
As soon as I figure it out, I'll add the information.

@cordx56
Copy link
Owner

cordx56 commented Feb 16, 2025

Ok, thank you! I wait your detailed information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants