eza: bug: thread 'main' panicked at library/std/src/sys/unix/time.rs:77:9: assertion failed: tv_nsec >= 0 && tv_nsec < NSEC_PER_SEC as i64
When i run the eza command on my home directory I get a crash:
output of eza --version:
$ eza --version
eza - A modern, maintained replacement for ls
v0.17.0 [+git]
https://github.com/eza-community/eza
The crash output:
thread 'main' panicked at library/std/src/sys/unix/time.rs:77:9:
assertion failed: tv_nsec >= 0 && tv_nsec < NSEC_PER_SEC as i64
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[1] 4728 IOT instruction /nix/store/v35mszl4kgcjc1v76dkfgw24lsbgn9ya-eza-0.17.0/bin/eza -abghHliSmxFuU
$ uname -a
Linux voidbox 6.5.13_1 #1 SMP PREEMPT_DYNAMIC Thu Nov 30 23:19:06 UTC 2023 x86_64 GNU/Linux
I have the same issue on version 0.16.3 that is availble on the void repo. I am using the latest build using nix.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 19 (10 by maintainers)
Commits related to this issue
- fix: update MSRV to 1.78 to solve rust malfunction This updated the rust MSRV to resolve a bug in the actual upstream rust implementation that has been affecting eza for a while. This obviously mean... — committed to eza-community/eza by cafkafk 2 years ago
- fix: update MSRV to 1.78 to solve rust malfunction This updated the rust MSRV to resolve a bug in the actual upstream rust implementation that has been affecting eza for a while. This obviously mean... — committed to eza-community/eza by cafkafk 2 years ago
I’m going to guess it doesn’t like that birth time! But either way,
ezashouldn’t crash. I’ll do a patch that should hide the issue, give me a few days.Oh I see. Sorry. I saw the new patch release and mistakenly assumed it included this change. I’ve cloned the repo and compiled from source - confirming that the issue is resolved.
Yep, that’s my understanding.
Hi @raxod502, did you compile from git main or the latest release? The updated MSRV is only in main at the moment. If you used main, can you compile a debug build and paste the stack trace from that? Thanks!
Sigh, after some digging this is the same issue as #666 where the standard library panics if the kernel gives it erroneous data for a file’s timestamps. Unfortunately we can’t fix this until the standard library has been updated.
Once again, caused by https://github.com/rust-lang/rust/issues/108277