vieiro commented on PR #9249:
URL: https://github.com/apache/netbeans/pull/9249#issuecomment-4027020461
FWIW, having the `rust-analyzer` use a log file may be of interest, because
it prints-out interesting stuff (maybe it hangs too?). This could be done using
a `System.property` pointing to a log file (say
`netbeans.rust.analyzer.log_file` or something). Who knows, maybe it's the
`rust-analyzer` process that is hanging causing GUI freeze.
For instance, if you mouse+click on a Rust `Result` in the editor, then the
corresponding `Result.rs` is opened (from the Rust `core` project). Then
`rust-analyzer` generates some errors in the `rust-analyzer.log` file:
```
$ cat /tmp/rust-analyzer.log
2026-03-09T22:19:58.76232392+01:00 ERROR failed fetching cargo workspace
root e=cd
"/home/antonio/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core"
&& "/home/antonio/.cargo/bin/cargo" "locate-project" "--workspace"
"--manifest-path"
"/home/antonio/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/Cargo.toml"
failed, exit status: 101
stderr:
error: failed to parse manifest at
`/home/antonio/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/Cargo.toml`
Caused by:
the cargo feature `profile-rustflags` requires a nightly version of Cargo,
but this is the `stable` channel
See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more
information about Rust release channels.
See
https://doc.rust-lang.org/cargo/reference/unstable.html#profile-rustflags-option
for more information about using this feature.
cargo_toml=/home/antonio/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/Cargo.toml
2026-03-09T22:20:00.679405718+01:00 ERROR failed fetching cargo workspace
root e=cd
"/home/antonio/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core"
&& "/home/antonio/.cargo/bin/cargo" "locate-project" "--workspace"
"--manifest-path"
"/home/antonio/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/Cargo.toml"
failed, exit status: 101
stderr:
error: failed to parse manifest at
`/home/antonio/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/Cargo.toml`
Caused by:
the cargo feature `profile-rustflags` requires a nightly version of Cargo,
but this is the `stable` channel
See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more
information about Rust release channels.
See
https://doc.rust-lang.org/cargo/reference/unstable.html#profile-rustflags-option
for more information about using this feature.
cargo_toml=/home/antonio/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/Cargo.toml
2026-03-09T22:20:01.200179926+01:00 ERROR failed fetching cargo workspace
root e=cd
"/home/antonio/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core"
&& "/home/antonio/.cargo/bin/cargo" "locate-project" "--workspace"
"--manifest-path"
"/home/antonio/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/Cargo.toml"
failed, exit status: 101
stderr:
error: failed to parse manifest at
`/home/antonio/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/Cargo.toml`
```
The process keeps on running well but who knows, maybe it causes a GUI
freeze in other circumstances...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
