sxyazi / yazi

💥 Blazing fast terminal file manager written in Rust, based on async I/O.
https://yazi-rs.github.io
MIT License
14.66k stars 331 forks source link

build from source minor warnings #1665

Open AnirudhG07 opened 2 hours ago

AnirudhG07 commented 2 hours ago

What system are you running Yazi on?

Linux X11

What terminal are you running Yazi in?

WezTerm

yazi --debug output

Probably not needed but still -

Yazi Debug ```Shell Yazi Version: 0.3.3 (7222e17 2024-09-20) Debug : false OS : linux-x86_64 (unix) Ya Version: 0.3.3 (7222e17 2024-09-20) Emulator Emulator.via_env: ("xterm-256color", "WezTerm") Emulator.via_csi: Ok(WezTerm) Emulator.detect : WezTerm Adapter Adapter.matches: Iip Desktop XDG_SESSION_TYPE : Some("x11") WAYLAND_DISPLAY : None DISPLAY : Some(":1") SWAYSOCK : None HYPRLAND_INSTANCE_SIGNATURE: None WAYFIRE_SOCKET : None SSH shared.in_ssh_connection: false WSL WSL: false Variables SHELL : Some("/bin/bash") EDITOR : Some("nvim") VISUAL : Some("nvim") YAZI_FILE_ONE : None YAZI_CONFIG_HOME : None Text Opener default: Some(Opener { run: "${EDITOR:=vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true }) block : Some(Opener { run: "${EDITOR:=vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true }) Multiplexers TMUX : false tmux version : 3.4 ZELLIJ_SESSION_NAME: None Zellij version : No such file or directory (os error 2) Dependencies file : 5.41 ueberzugpp : No such file or directory (os error 2) ffmpegthumbnailer: 2.2.2 magick : 7.1.1-36 fzf : 0.55.0 fd : 10.1.0 rg : 14.1.0 chafa : zoxide : 0.9.4 7z : 17.05 7zz : No such file or directory (os error 2) jq : 1.7.1 -------------------------------------------------- When reporting a bug, please also upload the `yazi.log` log file - only upload the most recent content by time. You can find it in the "/home/anirudhgupta/.local/state/yazi" directory. ```

Did you try the latest nightly build to see if the problem got fixed?

Yes, and I updated the debug information above (yazi --debug) to the nightly that I tried

Describe the bug

When i was building from source right now (time of issue). I got these warnings while building from source. Might as well let you know.

❯ cargo install --path yazi-fm; cargo install --path yazi-cli ``` Installing yazi-fm v0.3.3 (/home/anirudhgupta/yazi/yazi-fm) Updating crates.io index Locking 362 packages to latest compatible versions Adding aligned-vec v0.5.0 (latest: v0.6.1) Adding bitflags v1.3.2 (latest: v2.6.0) Adding cfg-expr v0.15.8 (latest: v0.17.0) Adding encode_unicode v0.3.6 (latest: v1.0.0) Adding event-listener v4.0.3 (latest: v5.3.1) Adding generic-array v0.14.7 (latest: v1.1.0) Adding hermit-abi v0.3.9 (latest: v0.4.0) Adding idna v0.5.0 (latest: v1.0.2) Adding inotify v0.10.2 (latest: v0.11.0) Adding itertools v0.12.1 (latest: v0.13.0) Adding linux-raw-sys v0.4.14 (latest: v0.6.5) Adding miniz_oxide v0.7.4 (latest: v0.8.0) Adding mio v0.8.11 (latest: v1.0.2) Adding nu-ansi-term v0.46.0 (latest: v0.50.1) Adding ordered-float v2.10.1 (latest: v4.2.2) Adding quick-xml v0.32.0 (latest: v0.36.1) Adding syn v1.0.109 (latest: v2.0.77) Adding system-deps v6.2.2 (latest: v7.0.2) Adding unicode-width v0.1.14 (latest: v0.2.0) Adding wasi v0.11.0+wasi-snapshot-preview1 (latest: v0.13.2+wasi-0.2.1) Adding windows v0.56.0 (latest: v0.58.0) Adding windows-core v0.52.0 (latest: v0.58.0) Adding windows-core v0.56.0 (latest: v0.58.0) Adding windows-implement v0.56.0 (latest: v0.58.0) Adding windows-interface v0.56.0 (latest: v0.58.0) Adding windows-result v0.1.2 (latest: v0.2.0) Adding windows-sys v0.48.0 (latest: v0.59.0) Adding windows-sys v0.52.0 (latest: v0.59.0) Adding windows-targets v0.48.5 (latest: v0.52.6) Adding windows_aarch64_gnullvm v0.48.5 (latest: v0.52.6) Adding windows_aarch64_msvc v0.48.5 (latest: v0.52.6) Adding windows_i686_gnu v0.48.5 (latest: v0.52.6) Adding windows_i686_msvc v0.48.5 (latest: v0.52.6) Adding windows_x86_64_gnu v0.48.5 (latest: v0.52.6) Adding windows_x86_64_gnullvm v0.48.5 (latest: v0.52.6) Adding windows_x86_64_msvc v0.48.5 (latest: v0.52.6) Adding winsafe v0.0.19 (latest: v0.0.22) warning: unused import: `FilesOp` --> yazi-scheduler/src/prework/prework.rs:9:39 | 9 | use yazi_shared::fs::{calculate_size, FilesOp, Url}; | ^^^^^^^ | = note: `#[warn(unused_imports)]` on by default warning: unused variable: `parent` --> yazi-scheduler/src/prework/prework.rs:94:10 | 94 | let parent = buf[0].0.parent_url().unwrap(); | ^^^^^^ help: if this is intentional, prefix it with an underscore: `_parent` | = note: `#[warn(unused_variables)]` on by default warning: `yazi-scheduler` (lib) generated 2 warnings (run `cargo fix --lib -p yazi-scheduler` to apply 1 suggestion) warning: unused variable: `cwd` --> yazi-core/src/manager/commands/bulk_rename.rs:50:3 | 50 | cwd: Url, | ^^^ help: if this is intentional, prefix it with an underscore: `_cwd` | = note: `#[warn(unused_variables)]` on by default warning: `yazi-core` (lib) generated 1 warning Compiling yazi-fm v0.3.3 (/home/anirudhgupta/yazi/yazi-fm) Finished `release` profile [optimized] target(s) in 1m 33s . . . ``` More to it, but the second command worked just fine.

Minimal reproducer

Just run the command mentioned above.

Anything else?

NA

sxyazi commented 2 hours ago

Yeah there is some ongoing work still not getting done, thanks for the report though!

AnirudhG07 commented 1 hour ago

Since it is in your notice, you can close this issue. It was meant only as a "just in case u didnt notice".