Skip Menu |

This queue is for tickets about the Catalyst-Plugin-Static-Simple CPAN distribution.

Report information
The Basics
Id: 83648
Status: open
Priority: 0/
Queue: Catalyst-Plugin-Static-Simple

People
Owner: Nobody in particular
Requestors: bitcard [...] 32ths.com
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.30
Fixed in: (no value)



Subject: set logging = 0 and module still logs when catalyst debug is turned on
15:37 < Savuud> | Hiya, quick question about the logging that Plugin::Static::Simple is creating when I'm running in debug mode. I've set the config 'logging' for 'Plugin::Static::Simple' to 0 but nothing seems to help! How can I get Static::Simple to not produce any log statements while running in debug mode? From Denny: 15:37 < denny> | this is an FAQ 15:37 < denny> | I think there's a bug in one of the modules somewhere that makes it not work as documented 15:37 < denny> | iirc 16:02 < denny> | Savuud: like I said, there's a bug 16:02 < denny> | I don't remember the details, but people have been through this at least twice in this channel in the last month or so So the options on IRC were 1. Deprecate this module (on cpan and elsewhere) and point to the replacements (Plack::App::File) 2. Fix this bug 3. ??? Version was Catalyst 5.9 This Module 0.30 - Mike
I can't reproduce this in a trivial testapp. Can you give me your Catalyst::Runtime version and you Catalyst::Plugin::Static::Simple version please, + your MyApp.pm class and info about any PSGI middleware you may be using via myapp.psgi? I'd love to get to the bottom of this - if it's allegedly well known, but we can't demonstrate it - we need to work out what's different for you, so we can reproduce and fix it.
I'm attaching the log of my example app / session (all components at latest version) to demonstrate how this doesn't happen for me:
Subject: example.ts
Download example.ts
application/octet-stream 6.7k

Message body not shown because it is not plain text.

On further thought - I'd speculate this is as you're using a non-default logging module (either Log4Perl or Log::Dispatch) - is that true?
From: bitcard [...] 32ths.com
Hi, I assume this is it as well. I'm not Savuud but since it was referenced as a FAQ (and had come up several times in a month), I felt obliged to file a bug since nobody else had. Savuud did mention Log4Perl but whether he used it to as a workaround to this problem or from the start, I do not know. As this can't be reproduced it seems logical to me to be an incompatibility with other logging modules. I think this logging option should not break with using non-default logging modules, it seems one of the design goals of catalyst in general is to select what modules you want to plug in, However, given this functionality is largely supplanted by other modules, it is probably not worth the time. At minimum, it should be documented. I can handle that if it makes it over to github. Thanks as always, - Mike On Tue Feb 26 16:52:43 2013, BOBTFISH wrote: Show quoted text
> On further thought - I'd speculate this is as you're using a non-default > logging module (either Log4Perl or Log::Dispatch) - is that true?
Subject: Re: [rt.cpan.org #83648] set logging = 0 and module still logs when catalyst debug is turned on
Date: Wed, 27 Feb 2013 07:57:10 +0000
To: bug-Catalyst-Plugin-Static-Simple [...] rt.cpan.org
From: Tomas Doran <bobtfish [...] bobtfish.net>
On 27 Feb 2013, at 03:27, "Mike W via RT" <bug-Catalyst-Plugin-Static-Simple@rt.cpan.org> wrote: Show quoted text
> > Thanks as always,
No, thank you for translating my complaints into a bug report. :-) I'll have a think about if we can more sensibly arrange things to suppress logging in other loggers. Cheers t0m
looks like this was fixed in commit 659bc603b5498eae0bf93e3f27b25e71331961fc by disabling autoflush, can anyone confirm this so I can close the ticket?