Skip to content
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

thread 'main' panicked; symlink issue? #30

Closed
dave-theunsub opened this issue Mar 5, 2023 · 1 comment · Fixed by #32
Closed

thread 'main' panicked; symlink issue? #30

dave-theunsub opened this issue Mar 5, 2023 · 1 comment · Fixed by #32

Comments

@dave-theunsub
Copy link

The et command works fine - except in my home directory:

thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/fs/erdtree/node.rs:271:28
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

The only difference I can see is that my home directory has links from other directories. Like this:

lrwxrwxrwx@   19 dave dave 26 Feb  2022 Documents -> /foo/Documents
lrwxrwxrwx@   16 dave dave 10 Jan  2022 Downloads -> /blah/Downloads

Any other ideas? Let me know if you require additional information. Using version 1.20.

backtrace.txt

@solidiquis
Copy link
Owner

Hey @dave-theunsub thanks for bringing this to my attention. I just merged in a fix for what I believe was the cause of the issue. I will include it in the next minor version release later today. Please let me know if the issue still persists; if so please feel free to re-open the issue!

tl;dr - I don't believe it was a symlink issue but rather there may be some files that you have whose names contain non-unicode sequences which caused my OsStr -> str conversion to panic. I opted instead to do lossy conversion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants