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

Bad error handling in fs::status for errors on the symlink target #107

Closed
gulrak opened this issue Mar 14, 2021 · 1 comment
Closed

Bad error handling in fs::status for errors on the symlink target #107

gulrak opened this issue Mar 14, 2021 · 1 comment
Assignees
Labels
available on master Fix is done on master branch, issue closed on next release bug Something isn't working POSIX POSIX type backend is affected
Milestone

Comments

@gulrak
Copy link
Owner

gulrak commented Mar 14, 2021

Describe the bug
The status result of symlinks to non-existing targets or targets that can not be accessed due to rights is wrong.

To Reproduce
Possible test path on Linux is /proc/1/task/1/cwd

Expected behavior
The error code should be set, file_type for symlinks to non-existing targets should be not_found.

@gulrak gulrak self-assigned this Mar 14, 2021
@gulrak gulrak added bug Something isn't working POSIX POSIX type backend is affected labels Mar 14, 2021
@gulrak gulrak added this to the v1.5.4 milestone Mar 14, 2021
@gulrak gulrak added the available on master Fix is done on master branch, issue closed on next release label Mar 14, 2021
@gulrak gulrak changed the title Bad error handling in fs::status on for errors on the symlink target Bad error handling in fs::status for errors on the symlink target Mar 15, 2021
@gulrak
Copy link
Owner Author

gulrak commented Mar 21, 2021

This is now part of release v1.5.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
available on master Fix is done on master branch, issue closed on next release bug Something isn't working POSIX POSIX type backend is affected
Projects
None yet
Development

No branches or pull requests

1 participant