-
-
Notifications
You must be signed in to change notification settings - Fork 257
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
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 #735
Comments
Hi @terminaldweller, are you able to narrow down which file is causing this? I can provide a debug build if it would help. |
it happens when i run the command in my home directory. not sure how I can figure out which file/dir is causing this? |
You can run Could you also let us know:
|
result of me running
|
as for a shorter version, removing |
#!/usr/bin/env bash
set -e
# for file in .*; do
for file in *; do
if [[ -f "$file" || -d "$file" ]]; then
echo "$file"
/tmp/fleshpit/pit1/eza/target/debug/eza -abghHliSmxFuU --color-scale all --git -@ "$file"
fi
done
I ran that on my home dir. eza broke down on my |
Can you run |
$ stat Cookies [INSERT] 50mS 101↵ L2
File: Cookies
Size: 1179648 Blocks: 2304 IO Block: 4096 regular file
Device: 0,48 Inode: 12849014 Links: 1
Access: (0600/-rw-------) Uid: ( 1000/ devi) Gid: ( 1000/ devi)
Access: 2023-12-20 09:05:35.153917959 -0500
Modify: 2023-12-20 09:05:35.157917960 -0500
Change: 2023-12-20 09:05:35.157917960 -0500
Birth: 3977857371630039149.876097842 |
I'm going to guess it doesn't like that birth time! But either way, |
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 rust-lang/rust#108277 |
Seems like this issue could be also closed? |
Panic still occurs for me using eza 0.20.17. I see that the upstream bug report has been closed since a patch was merged. Does eza just need to upgrade to a newer rust version to pick up the fix? |
Yep, that's my understanding. |
What version is nescesarry? we may consider bumping the MSRV if appropriate |
Looks like 1.78: rust-lang/rust@e69f14b |
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 means new eza releases won't be available on all distributions, but those distributions should move to a new version of rust then, since this bug seems to indicate that there is an important issue here. Closes: #735 Refs: #666 rust-lang/rust@e69f14b Signed-off-by: Christina Sørensen <ces@fem.gg>
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 means new eza releases won't be available on all distributions, but those distributions should move to a new version of rust then, since this bug seems to indicate that there is an important issue here. Closes: #735 Refs: #666 rust-lang/rust@e69f14b Signed-off-by: Christina Sørensen <ces@fem.gg>
It still appears to be an issue for me, although I have just now realized that it only happens when using the
|
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! |
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. |
When i run the eza command on my home directory I get a crash:
output of
eza --version
:The crash output:
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.
The text was updated successfully, but these errors were encountered: