nushell: panicked nu shell. ls \\.\pipe\\ No such local time

Listing windows pipes crashes nu

nu -e “ls \.\pipe\”

 ls \\.\pipe\\                                                              09/21/23 23:39:23 PM
Failed to read metadata for '\\.\pipe\uv\0000000000000000-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000000-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000001-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000001-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000002-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000002-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000002-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000003-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000003-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000004-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000004-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000005-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000005-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000006-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000007-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000007-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000007-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000008-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000008-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000008-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000009-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000009-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000009-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000A-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000A-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000B-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000B-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000C-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000C-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000D-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000E-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000010-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000011-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000012-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000013-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000014-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000015-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000015-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000016-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000016-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000017-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000017-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000018-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000019-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001A-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001B-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001C-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001D-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001D-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001E-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001F-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000020-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000020-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000020-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000021-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000021-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000022-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000022-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000023-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000023-36912'. It may have an illegal filename
thread 'main' panicked at C:\Users\dhorner\.cargo\registry\src\index.crates.io-6f17d22bba15001f\chrono-0.4.31\src\offset\local\mod.rs:176:46:
No such local time
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: process didn't exit successfully: `target\release\nu.exe` (exit code: 101)

How to reproduce

start a nu shell on windows; ls \.\pipe\

Expected behavior

should get the same results as: dir /b \.\pipe\

I will note that the /b is nice to use because even dir has trouble listing the contents of this folder.

The parameter is incorrect.
◄♂                   1 ConEmuSrv13408
The parameter is incorrect.
☻►                   1 ConEmuHk37048
The parameter is incorrect.
☻♫                   1 ConEmuSrv224
The parameter is incorrect.
☻♫                   1 ConEmuHk15152
The parameter is incorrect.
☻♫                   1 ConEmuSrv38244
The parameter is incorrect.
☻♫                   1 ConEmuSrvRead224
The parameter is incorrect.
☻♫                   1 ConEmuSrv34036
The parameter is incorrect.
☻♫                   1 ConEmuSrvInput224
The parameter is incorrect.
◄♣                   1 ConEmuSrvInput13408
The parameter is incorrect.
◄                          1 ConEmuSrvRead13408
The parameter is incorrect.
◄                   1 ConEmuHk14908
The parameter is incorrect.
☻♫                   1 ConEmuHk29876
...and the list goes on...

Screenshots

No response

Configuration

c:/working/rust/nushell> version | transpose key value | to md --pretty 09/21/23 23:45:33 PM

key	value
version	0.85.1
branch	main
commit_hash	1bb953877e0c574bf28e9033210684bd82a2c820
build_os	windows-x86_64
build_target	x86_64-pc-windows-msvc
rust_version	rustc 1.74.0-nightly (3223b0b5e 2023-09-20)
cargo_version	cargo 1.74.0-nightly (b4ddf95ad 2023-09-18)
build_time	2023-09-21 18:21:53 -04:00
build_rust_channel	release
allocator	mimalloc
features	default, sqlite, trash, which, zip
installed_plugins

Additional context

full backtrace:

Failed to read metadata for '\\.\pipe\uv\0000000000000000-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000000-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000001-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000001-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000002-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000002-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000002-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000003-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000003-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000004-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000004-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000005-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000005-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000006-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000007-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000007-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000007-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000008-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000008-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000008-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000009-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000009-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000009-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000A-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000A-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000B-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000B-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000C-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000C-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000D-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000000E-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000010-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000011-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000012-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000013-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000014-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000015-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000015-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000016-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000016-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000017-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000017-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000018-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000019-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001A-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001B-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001C-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001D-15212'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001D-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001E-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\000000000000001F-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000020-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000020-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000020-7668'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000021-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000021-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000022-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000022-36912'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000023-10028'. It may have an illegal filename
Failed to read metadata for '\\.\pipe\uv\0000000000000023-36912'. It may have an illegal filename
thread 'main' panicked at C:\Users\dhorner\.cargo\registry\src\index.crates.io-6f17d22bba15001f\chrono-0.4.31\src\offset\local\mod.rs:176:46:
No such local time
stack backtrace:
   0:     0x7ff76250243f - <unknown>
   1:     0x7ff7618dde8b - <unknown>
   2:     0x7ff7624fc221 - <unknown>
   3:     0x7ff7625021ba - <unknown>
   4:     0x7ff762504d29 - <unknown>
   5:     0x7ff7625049bd - <unknown>
   6:     0x7ff7625054e0 - <unknown>
   7:     0x7ff76250521b - <unknown>
   8:     0x7ff762503099 - <unknown>
   9:     0x7ff762504f94 - <unknown>
  10:     0x7ff7626e9d37 - <unknown>
  11:     0x7ff7618cb2be - <unknown>
  12:     0x7ff761bd8351 - <unknown>
  13:     0x7ff761bb81a9 - <unknown>
  14:     0x7ff761b05095 - <unknown>
  15:     0x7ff761c749b3 - <unknown>
  16:     0x7ff761e00dad - <unknown>
  17:     0x7ff76237f681 - <unknown>
  18:     0x7ff76236451d - <unknown>
  19:     0x7ff762363539 - <unknown>
  20:     0x7ff7619f8437 - <unknown>
  21:     0x7ff7619c2b22 - <unknown>
  22:     0x7ff7619a9b2d - <unknown>
  23:     0x7ff761999c15 - <unknown>
  24:     0x7ff7619a3a76 - <unknown>
  25:     0x7ff7619ad728 - <unknown>
  26:     0x7ff7624f5378 - <unknown>
  27:     0x7ff76199b9dc - <unknown>
  28:     0x7ff7626d09ac - <unknown>
  29:     0x7ffe865b7344 - BaseThreadInitThunk
  30:     0x7ffe87ba26b1 - RtlUserThreadStart
error: process didn't exit successfully: `target\release\nu.exe` (exit code: 101)

About this issue

Original URL
State: closed
Created 9 months ago
Comments: 26 (17 by maintainers)

Commits related to this issue

fix panic caused by `ls \\.\pipe` (#10558) wrap chrono in panic hooks to handle panic'ing unwraps on Jan 1, 1601 00:00 UTC and other reasons unknown. An overflow if time_u64 is smaller than EPOCH_A... — committed to nushell/nushell by davehorner 5 months ago
fix panic caused by `ls \\.\pipe` (#10558) wrap chrono in panic hooks to handle panic'ing unwraps on Jan 1, 1601 00:00 UTC and other reasons unknown. An overflow if time_u64 is smaller than EPOCH_A... — committed to dmatos2012/nushell by davehorner 5 months ago

Most upvoted comments

To be precise, it’s Jan 1, 1601 00:00 UTC. So you’ll need to convert to your local time.

ChrisDenton on Sep 22, 2023

PR is pending. Thanks https://github.com/nushell/nushell/pull/10558

davehorner on Sep 30, 2023

I’m good with whatever works.

fdncred on Sep 30, 2023