exa: Panic when `--long` is used

# exa v0.8.0

$ RUST_BACKTRACE=1 exa -l
thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', /build/rust/src/rustc-1.33.0-src/src/libcore/slice/mod.rs:2455:10
stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: __libc_start_main
  14: <unknown>
Aborted (core dumped)

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 36
Comments: 27 (3 by maintainers)

Links to this issue

Commits related to this issue

`exa` is broken; use `ls` See https://github.com/ogham/exa/issues/517. — committed to nutty7t/dotfiles by deleted user 5 years ago
Revert to coreutils ls until exa is fixed https://github.com/ogham/exa/issues/517 — committed to JackCuthbert/dotfiles by JackCuthbert 5 years ago
`exa` is broken; use `ls` See https://github.com/ogham/exa/issues/517. — committed to nutty7t/dotfiles by nutty7t 5 years ago

Most upvoted comments

The crash is triggered by the update to tzdata 2019b. Rolling back to 2019a avoids it.

+12

AluisioASG on Jul 8, 2019

The PR for zoneinfo-compiled linked above (https://github.com/rust-datetime/zoneinfo-compiled/pull/8) contains the relevant fix!

I could reproduce the crash with the uploaded Sydney and /etc/localtime files (thanks for all of those). After building again with the new version of zoneinfo-compiled, it doesn’t crash anymore.

ogham on Jul 14, 2019

If don’t want to downgrade, you may want to give lsd a try.

blackadress on Jul 9, 2019

It fails for every timezone

from pytz import all_timezones
from re import match
from os import system


for tz in filter(lambda x: match(r'^[a-zA-Z/]+$', x), all_timezones):
    system('TZ=%s exa -l 2>/dev/null' % tz)

pangteypiyush on Jul 8, 2019

I’m having the same issue, if it’s useful, my timezone is America/Lima, using ArchLinux This is that I get while running exa -l and as the error message said, running with RUST_BACKTRACE=1 too

 exa -l
thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', /build/rust/src/rustc-1.33.0-src/src/libcore/slice/mod.rs:2455:10
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
[1]    7616 abort (core dumped)  exa -l

 export RUST_BACKTRACE=1                                                                                                             

 exa -l
thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', /build/rust/src/rustc-1.33.0-src/src/libcore/slice/mod.rs:2455:10
stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: __libc_start_main
  14: <unknown>
[1]    7916 abort (core dumped)  exa -l

c0x6a on Jul 6, 2019

This seems to happen with only some specific timezone (exa read them from /etc/localtime). On my side Asia/Tokyo and America/Los_angeles work just fine, but Asia/Shanghai and Asia/Hong_kong will cause the panic.

hiecaq on Jul 5, 2019

Same here: America/Sao_Paulo

brunobertoldi on Jul 9, 2019

I believe I’m getting the same error with the Pacific/Auckland timezone and Exa 0.8.0 on Arch Linux.

severen on Jul 6, 2019

This is affecting all my systems, across different timezones.

dessalines on Jul 11, 2019

Happening here too with Australia/Sydney.

abusch on Jul 8, 2019