[Bug]: Main thread panics in a particular directory

[matterhorn103]

Version

• latest

version

1.1.2

What OS are you seeing the problem on?

Linux

installation

With zypper from openSUSE base repo.

term

xterm-256color

ls-colors

(an empty line)

What happened?

I get a thread panic when running `lsd` in the following directory that displays fine with `ls`:


$ ls -la
total 40
drwxr-xr-x 2 matt matt    8192 Jul 25 11:02  ./
drwxr-xr-x 2 matt matt    8192 Aug 18  2023  ../
-rwxr-xr-x 1 matt matt 2797766 Apr 29  2022  Abc-Abc-Abc_SI-April.docx*
-rwxr-xr-x 1 matt matt 2802556 May  4  2022  Abc-Abc-Abc_SI-April_M.docx*
-rwxr-xr-x 1 matt matt 4484794 Jun 24  2022  Abc-Abc-Abc_SI-June_M.docx*
-rwxr-xr-x 1 matt matt 4504965 Mar 24  2023  Abc-Abc-Abc_SI-March_2023.docx*
-rwxr-xr-x 1 matt matt 4584807 Jun  6  2023  Abc-Abc-Abc_SI-May-2023.docx*
-rwxr-xr-x 1 matt matt 3872490 Feb 24  2022 'bT M 2022-02-22.docx'*
-rwxr-xr-x 1 matt matt   19289 Jan 10  2022  bT_si_v0.1.docx*
-rwxr-xr-x 1 matt matt   80032 Jan 19  2022  bT_si_v0.2.docx*
drwxr-xr-x 2 matt matt       0 Sep 22  1881  c_E_data/
-rwxr-xr-x 1 matt matt  274416 Aug  2  2023  fig4.png*
-rwxr-xr-x 1 matt matt  285688 Aug  2  2023  fig5.png*
drwxr-xr-x 2 matt matt       0 Aug 18  2023 'Mail 13.05.2022'/
drwxr-xr-x 2 matt matt       0 Aug 18  2023  mail_2023-06-06/
drwxr-xr-x 2 matt matt       0 Aug 18  2023  mail_2023-06-27/
-rwxr-xr-x 1 matt matt 1725578 May  4  2022 'P_Di-April 2022_M.docx'*
-rwxr-xr-x 1 matt matt 1723661 Jun 24  2022 'P_Di-June 2022_M.docx'*
-rwxr-xr-x 1 matt matt 1729218 Jun  6  2023  P_Di-June-2023-M.docx*
-rwxr-xr-x 1 matt matt 1698709 Mar 24  2023  P_Di-March_2023.docx*
-rwxr-xr-x 1 matt matt 1721573 Jun  6  2023  P_Di-May-2023.docx*
drwxr-xr-x 2 matt matt       0 Aug 18  2023  s_d/
-rwxr-xr-x 1 matt matt  742305 Aug  2  2023  S_P_Di_all.xlsx*
-rwxr-xr-x 1 matt matt  639917 Jun  7  2023  S_P_Di_New.xlsx*

Note that I abbreviated long purely alphabetical strings to single letters for reasons of data sensitivity.

### What expected?

```markdown
With `RUST_BACKTRACE=1`:

thread 'main' panicked at library/std/src/sys/pal/unix/time.rs:103:9:
assertion failed: tv_nsec >= 0 && tv_nsec < NSEC_PER_SEC as i64
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

With RUST_BACKTRACE=full:

thread 'main' panicked at library/std/src/sys/pal/unix/time.rs:103:9:
assertion failed: tv_nsec >= 0 && tv_nsec < NSEC_PER_SEC as i64
stack backtrace:
   0:     0x55911c502943 - <unknown>
   1:     0x55911c43b3a0 - <unknown>
   2:     0x55911c50e07d - <unknown>
   3:     0x55911c503398 - <unknown>
   4:     0x55911c503272 - <unknown>
   5:     0x55911c503b33 - <unknown>
   6:     0x55911c5035c8 - <unknown>
   7:     0x55911c503556 - <unknown>
   8:     0x55911c503543 - <unknown>
   9:     0x55911c338fe4 - <unknown>
  10:     0x55911c339182 - <unknown>
  11:     0x55911c37032f - <unknown>
  12:     0x55911c3727e4 - <unknown>
  13:     0x55911c349b1c - <unknown>
  14:     0x55911c343773 - <unknown>
  15:     0x55911c343db9 - <unknown>
  16:     0x7f85f422a1f0 - __libc_start_call_main
  17:     0x7f85f422a2b9 - __libc_start_main@GLIBC_2.2.5
  18:     0x55911c343175 - <unknown>
  19:                0x0 - <unknown>

### What else?

```markdown
It might be of relevance that this is on a samba server mounted via cifs.