I was wondering though if you could maybe shed some light on why this issue only seems to happen sometimes?
We use Path::Class::Dir in our codebase in a bunch of places, but this issue only popped up recently. Additionally the error only happens in certain situations that I have not been able to track down. I tried looking at the Path::Class::Entity source to see if I could figure out why but made no headway.
So if you could also shed some light on what circumstances make $_[0] a ref instead of a scalar it would be appreciated.
Regardless though the patch does fix the issue for us.
I ran into this issue.. https://rt.cpan.org/Public/Bug/Display.html?id=77259 The patch listed there fixes our issue. This PR is simply that patch.
I was wondering though if you could maybe shed some light on why this issue only seems to happen sometimes? We use Path::Class::Dir in our codebase in a bunch of places, but this issue only popped up recently. Additionally the error only happens in certain situations that I have not been able to track down. I tried looking at the Path::Class::Entity source to see if I could figure out why but made no headway. So if you could also shed some light on what circumstances make $_[0] a ref instead of a scalar it would be appreciated.
Regardless though the patch does fix the issue for us.