exa: Panicked at called Result::unwrap()

I am using the exa version v0.9.0 on a MacOS Catalina 10.15.7

Into a GIT project I am running into the following error, launching the command:

ls

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/libcore/result.rs:1084:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

Removing .git folder, the issue disappears
Launching exa -la, the issue disappears

Thank you

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 8
Comments: 21

Most upvoted comments

I see, good luck! @ogham any ETA on a new release?

viluon on Jan 8, 2021

As I said above,

I mean, a panic is as general as a segfault… However as said here the SystemTimeError is very probably the one that has been fixed a while ago.

ariasuni on Jan 29, 2021

Nice summary @ariasuni. Although the relevant issues seem to be fixed, users (me included) are still encountering them because there hasn’t been a release incorporating the fixes. Is there a good reason for that?

viluon on Jan 7, 2021

Similar here (ubuntu 20.10 with exa from official repo), removing the .git folder doesn’t help nor running exa -la.

It’s the -l option to cause this (-a and -h or without options, it works)

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: SystemTimeError(2147483648s)', src/fs/file.rs:331:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[1]    7916 abort (core dumped)  exa -lh

tommyblue on Jan 1, 2021