-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Error when running ls -la
: thread 'main' panicked at 'assertion failed
#8769
Comments
Looks like you have a file with an incorrect time maybe? We should handle this better though. |
Hmmm. Let's see, this is the file size and date/time columns of
|
LOL. I don't think bash is written in rust so it doesn't uss the same crate source code such as Someone may be able to fix this in the nushell source but it could also be an upstream problem as well, I'm not sure. Without having a file that produces these errors, it'll be hard to fix though. |
edit: @fdncred is right about the |
I don't think it's the directory that's causing the problems. There is probably 1 file with a messed up access, modify, change, or birth date that is funky that is causing |
I have problematic files. Like this one:
How do I know? Because inside nushell Other problematic file, for comparisson:
And a good file:
|
And just for completeness, my |
I think you've put your finger on what the issue is but it's going to take someone, like yourself, with those messed up dates, to try and make nushell's ls code behave and not panic in those situations. |
Thanks. I found out the Rust devs are already aware of this problem. |
The upstream bug has been fixed in 1.78.0 (the minimum version nushell builds with now). @llagerlof would you mind testing with a fresh nushell version? |
Unfortunately I don't have access to that filesystem anymore. |
Describe the bug
Inside
nushell
(0.78.0), the error below are happening when I issue the commandls -la
:How to reproduce
nu
ls -la
Expected behavior
List all files and directories inside the current directory.
Screenshots
No response
Configuration
Additional context
The text was updated successfully, but these errors were encountered: