-
Notifications
You must be signed in to change notification settings - Fork 38
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
Implement support for following symlinks #131
Conversation
Codecov Report
@@ Coverage Diff @@
## main #131 +/- ##
==========================================
- Coverage 52.52% 50.56% -1.97%
==========================================
Files 23 19 -4
Lines 4655 2589 -2066
Branches 1531 688 -843
==========================================
- Hits 2445 1309 -1136
+ Misses 1664 1039 -625
+ Partials 546 241 -305
Continue to review full report at Codecov.
|
80c0577
to
9492b36
Compare
Clap clap:
|
Ah nice! This seems to affect quite a few tests. Any ideas for how to handle the walkdir issue, though? |
The initial release of findutils was pinned to a specific version in my
branch of walkdir, while I waited for
BurntSushi/walkdir#19 to be accepted and included
in a release.
So it's not without precedent.
Long term, I'd suggest giving it a few months and then making our own
branch if the PRs keep piling up there untouched?
Mark
…On Mon, Jan 24, 2022 at 3:04 PM Ryan Gonzalez ***@***.***> wrote:
Ah nice! This seems to affect quite a few tests. Any ideas for how to
handle the walkdir issue, though?
—
Reply to this email directly, view it on GitHub
<#131 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC3MQF34BO2IMWYGHUX2HT3UXVTAZANCNFSM5MQ65VVA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Signed-off-by: Ryan Gonzalez <[email protected]>
9492b36
to
29e5f52
Compare
It is possible to work around BurntSushi/walkdir#160 the same way |
@tavianator I was originally going to try using a similar system here, but there were 2 things that made me go with the walkdir patches instead:
That being said, if the walkdir PR stays stagnant for too long, it may be worth switching over. |
no activity for a while, closing |
Signed-off-by: Ryan Gonzalez [email protected]
Unfortunately, it wasn't possible to make work as needed without these two PRs to walkdir: BurntSushi/walkdir#159 BurntSushi/walkdir#160
However, it seems that PRs to walkdir have been stagnant since late 2020 / early 2021, so for the purpose of testing, I created a single branch on my fork with both PRs merged in, and Cargo.toml in here is pointing to that branch. I'm not quite sure how to handle this as a result, so this is in draft status. Any thoughts on how to handle this?