Closed pghmcfc closed 7 years ago
This really should be fixed in Log::Any::Adapter::Dispatch. It's passing arguments to Log::Dispatch that Log::Dispatch does not, and never did, accept.
It looks like the repository is https://github.com/jonswar/perl-log-any-adapter-dispatch. I've got ownership of the main Log-Any dist, and I could help you (@pghmcfc) with getting a patch in and released (going through the PAUSE admins to get releaser privileges for you or me if @jonswar is indeed out of communication). But I agree it's not Log::Dispatch's fault that the Log-Any adapter has always done something wrong.
@preaction, I think you're a better candidate for this than I am, as my interest is mainly as a downstream packager of something that has Log::Any::Adapter::Dispatch as a dependency. I noticed the failure in Fedora's continuous integration system, koschei. I don't actually have a PAUSE account myself.
I'd be happy to help out with testing if that's any help.
I have no stake in this at all except as the maintainer of Log-Any and a wish to see a healthy Log-Any (and CPAN in general) ecosystem. Please open the bug against the other Github project. We'll see if jonswar picks it up. If he doesn't, I can't provide a patch, so I'd need you to do that. Once a patch is provided, I can help get it uploaded to CPAN, but I would also prefer you to do that (PAUSE accounts are free, after all). I mostly offered to help you navigate the process for taking over a module in CPAN if jonswar is not available to add you to the list of authorized maintainers.
But the summary is: This is not a problem with Log::Dispatch and this ticket should be closed.
Closing.
For anyone who comes across this later, this issue has been fixed in https://github.com/preaction/Log-Any-Adapter-Dispatch/commit/eb7f74b60f31a6ca14a3393c1208fc7509ea89f9 and released to CPAN as Log::Any::Adapter::Dispatch v0.07.
See http://www.cpantesters.org/cpan/report/206238d6-f1c6-11e6-bb94-6bc77d6e3ab9 for example:
I don't know if that module is doing something unsupported or if something got missed in the switch to Params::ValidationCompiler, but Log-Any-Adapter-Dispatch hasn't changed since 2010 so I guess it's not actively maintained.
It's still failing with 2.62 but you don't get the (possibly useful) stack trace.