You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear Leon
thanks for correlating these bugs. I'm a total newby with GitHub and
couldn't search it for like bugs.
Having quickly read #19995 and #20008 I cannot judge whether they are
the same bug. However I did provide a fairly explicit means to
reproduce my bug which tests out on Win7 and Win10 (and DOS). And I
traced it to a particular usage of CD which broke it. So if #20008
fixes my bug too then they are indeed the same bug...
Nice to find that maintenance is still live :)
Regards Rob
On 9/16/22, Leon Timmermans ***@***.***> wrote:
I suspect this is the same bug as #19995
and should be fixed by #20008
--
Reply to this email directly or view it on GitHub:
#20306 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
Module:File::Find
Description
In windows a stupidly long and straggly directory structure can defeat the find() traverse process.
bug_report.txt
Steps to Reproduce
run these scripts (usage is in bug_report.txt above)
mk_tst.bat.txt
tst_find.bat.txt
tst_find_log.bat.txt
GitHub rejects .bat files, so you'll have to strip their .txt suffix
From the 3rd script I got
STDOUT tst_find_1.log
STDERR tst_find_2.log
(produced on a Win7 system)
Expected behavior
That find() shall traverse any possible tree, even one constructed through incompetence, malice, or runaway software.
Pro tem I butchered my copy of find.pm - see bug_report.txt above
Perl configuration
The text was updated successfully, but these errors were encountered: