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

Mac SDK: DirectoryInfo.EnumerateDirectories and DirectoryInfo.EnumerateFiles Method does not handle symbolic link very well #34363

Closed
Tracked by #57205 ...
bahdah opened this issue Feb 8, 2020 · 5 comments

Comments

@bahdah
Copy link

bahdah commented Feb 8, 2020

Issue Title

Mac SDK: DirectoryInfo.EnumerateDirectories Method does not handle symbolic link very well

General

I made a recursive call to DirectoryInfo.EnumerateDirectories to get subdirectories and files.
It works on Windows 10 and Ubuntu 18.04. However, it crashes on Mac OS High Sierra 10.13.6. After further investigation, it seems to be caught in an infinite loop when it detects a symbolic link.
I tried to replicate the issue on Windows 10 and the code seems to ignore them. I haven't tested Ubuntu yet.

If the expectation is to allow the method to be consistent in both Mac and Windows, I think this should be considered a bug.

@ghost
Copy link

ghost commented Feb 9, 2020

Have you got any kind of stack trace for this?

@scalablecory scalablecory transferred this issue from dotnet/core Apr 1, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Apr 1, 2020
@Dotnet-GitSync-Bot
Copy link
Collaborator

I couldn't figure out the best area label to add to this issue. Please help me learn by adding exactly one area label.

@ghost
Copy link

ghost commented Apr 1, 2020

Area Owners

@JeremyKuhne, @carlossanlop, @jozkee

@carlossanlop carlossanlop added bug and removed untriaged New issue has not been triaged by the area owner labels Apr 23, 2020
@carlossanlop carlossanlop added this to the 5.0 milestone Apr 23, 2020
@carlossanlop carlossanlop modified the milestones: 5.0.0, Future Jun 18, 2020
Copy link
Contributor

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@dotnet-policy-service dotnet-policy-service bot added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels Dec 19, 2024
Copy link
Contributor

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

@dotnet-policy-service dotnet-policy-service bot removed this from the Future milestone Jan 2, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Feb 1, 2025
@dotnet-policy-service dotnet-policy-service bot removed no-recent-activity backlog-cleanup-candidate An inactive issue that has been marked for automated closure. labels Feb 1, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants