EdJoPaTo / tui-rs-tree-widget

Tree Widget for tui-rs
https://crates.io/crates/tui-tree-widget
MIT License
60 stars 16 forks source link

Library requires nightly? #29

Open Cypressxyx opened 1 week ago

Cypressxyx commented 1 week ago

Hello,

I am currently using this in a project of mine (see https://github.com/Cypressxyx/lazycurl/commit/672a9361011f57a97c11d60d97444fb97d3e2d95)

and it appears like installing this somehow broke my LSP for lunarvim.

I am not sure why, the only error I saw was

[ERROR][2024-04-20 14:31:36] .../vim/lsp/rpc.lua:734    "rpc"   "rust-analyzer" "stderr"    '2024-04-20T21:31:36.172333Z ERROR rust_analyzer::main_loop: FetchWorkspaceError:\nrust-analyzer failed to load workspace: Failed to load the project at /Users/<username>/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/library/std/Cargo.toml: Failed to read Cargo metadata from Cargo.toml file /Users/<username>/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/library/std/Cargo.toml, Some(Version { major: 1, minor: 76, patch: 0 }): Failed to run `cd "/Users/<username>/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/library/std" && "cargo" "metadata" "--format-version" "1" "--manifest-path" "/Users/<username>/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/library/std/Cargo.toml" "--filter-platform" "x86_64-apple-darwin"`: `cargo metadata` exited with an error: error: failed to parse manifest at `/Users/<username>/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/library/std/Cargo.toml`\n\nCaused by:\n  the cargo feature `public-dependency` requires a nightly version of Cargo, but this is the `stable` channel\n  See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.\n  See https://doc.rust-lang.org/cargo/reference/unstable.html#public-dependency for more information about using this feature.\n\n\n'

switching the cargo to nightly allowed my LSP to work again.

Not sure if this is directly related to the package, however opening as issue in case someone runs into a similar problem

EdJoPaTo commented 1 week ago

Nope, this works on stable and is also tested via CI on stable.

I also don’t know what causes your issue. Maybe cargo clean and build on a clean target folder again?