Bug #84544 for Log-Dispatch-File-Stamped: Not all Log::Dispatch::File options are respected

Tue Apr 09 19:22:17 2013 ether [...] cpan.org - Ticket created

CC:	modules [...] perl.lorg
Subject:	Not all Log::Dispatch::File options are respected
Date:	Tue, 9 Apr 2013 16:22:03 -0700
To:	bug-Log-Dispatch-File-Stamped [...] rt.cpan.org
From:	Karen Etheridge <ether [...] cpan.org>

Log::Dispatch::File optionally does a number of nice things, like bypassing block buffering, closing the filehandle after every write, etc that this module does not handle. (From t/other_options.t in the below-mentioned repository, the options that are currently not respected are: autoflush, close_after_write, mode, and syswrite.) As I really would like to use timestamped files, but keep using the existing settings that I need in production, I've fixed this module as well as made some modifications to Log::Dispatch::File itself to make subclassing a little easier. Dave Rolsky has my fixes for Log::Dispatch::File at https://github.com/karenetheridge/Log-Dispatch/tree/topic/fix_subclassing. I've rewritten ::File::Stamped to do the right thing in all cases, as well as writing tests to confirm this, at https://github.com/karenetheridge/Log-Dispatch-File-Stamped (using the 0.10 release as a starting point). I'm happy to do anything extra that is needed to help get this into a releasable state, up to and including taking on comaint of this module in case you are busy/no longer interested in Perl development and/or maintaining this module -- but no pressure, it's totally fine if you don't want to take that route, too! cc: modules@perl.org thanks, Karen Etheridge ether@cpan.org

Tue Apr 09 19:22:47 2013 ether [...] cpan.org - Status changed from 'new' to 'patched'

Tue Apr 09 19:22:47 2013 ether [...] cpan.org - Severity Normal added

Tue Apr 09 19:22:47 2013 ether [...] cpan.org - Broken in 0.10 added

Tue Apr 09 19:28:38 2013 ether [...] cpan.org - Dependency on ticket #84545 added

Mon Apr 22 17:39:47 2013 ether [...] cpan.org - Correspondence added

RT-Send-CC:

modules [...] perl.org

Log-Dispatch-File-Stamped-0.10_002 has been uploaded to PAUSE as an unauthorized release, as my $company is using it in its production code now, but I'd really like this to get your blessing :) (cc modules@perl.org - this is the third attempt to contact you over a span of a few months -- earlier attempts are when I filed this ticket, and when I inquired about a public repository and/or process for patching, via https://rt.cpan.org/Ticket/Display.html?id=84228) On Tue Apr 09 16:22:17 2013, ETHER wrote: Show quoted text

> > Log::Dispatch::File optionally does a number of nice things, like bypassing > block buffering, closing the filehandle after every write, etc that this > module does not handle. (From t/other_options.t in the below-mentioned > repository, the options that are currently not respected are: autoflush, > close_after_write, mode, and syswrite.) > > As I really would like to use timestamped files, but keep using the > existing settings that I need in production, I've fixed this module as well > as made some modifications to Log::Dispatch::File itself to make > subclassing a little easier. > > Dave Rolsky has my fixes for Log::Dispatch::File at > https://github.com/karenetheridge/Log-Dispatch/tree/topic/fix_subclassing. > > I've rewritten ::File::Stamped to do the right thing in all cases, as well > as writing tests to confirm this, at > https://github.com/karenetheridge/Log-Dispatch-File-Stamped (using the 0.10 > release as a starting point). > > I'm happy to do anything extra that is needed to help get this into a > releasable state, up to and including taking on comaint of this module in > case you are busy/no longer interested in Perl development and/or > maintaining this module -- but no pressure, it's totally fine if you don't > want to take that route, too! > > cc: modules@perl.org > > thanks, > > Karen Etheridge > ether@cpan.org

Mon Jun 10 17:50:41 2013 ether [...] cpan.org - Correspondence added

RT-Send-CC:

modules [...] perl.lorg

It has been six weeks since my last ping, and I haven't heard from you, since trying to reach you since March. This message is an official request to modules@perl.org to formally adopt Log::Dispatch::File::Stamped so I can get the aforementioned rewrites into the PAUSE index. (Log-Dispatch-File-Stamped-0.10_010 has been up for over a month, with no failure reports.) On 2013-04-22 14:39:47, ETHER wrote: Show quoted text

> > Log-Dispatch-File-Stamped-0.10_002 has been uploaded to PAUSE as an > unauthorized release, as my $company is using it in its production > code now, but I'd really like this to get your blessing :) > > (cc modules@perl.org - this is the third attempt to contact you over a > span of a few months -- earlier attempts are when I filed this > ticket, and when I inquired about a public repository and/or > process for patching, via > https://rt.cpan.org/Ticket/Display.html?id=84228) > > > On Tue Apr 09 16:22:17 2013, ETHER wrote:

> > > > Log::Dispatch::File optionally does a number of nice things, like

> bypassing

> > block buffering, closing the filehandle after every write, etc that

> this

> > module does not handle. (From t/other_options.t in the below-

> mentioned

> > repository, the options that are currently not respected are:

> autoflush,

> > close_after_write, mode, and syswrite.) > > > > As I really would like to use timestamped files, but keep using the > > existing settings that I need in production, I've fixed this module

> as well

> > as made some modifications to Log::Dispatch::File itself to make > > subclassing a little easier. > > > > Dave Rolsky has my fixes for Log::Dispatch::File at > > https://github.com/karenetheridge/Log-

> Dispatch/tree/topic/fix_subclassing.

> > > > I've rewritten ::File::Stamped to do the right thing in all cases,

> as well

> > as writing tests to confirm this, at > > https://github.com/karenetheridge/Log-Dispatch-File-Stamped (using

> the 0.10

> > release as a starting point). > > > > I'm happy to do anything extra that is needed to help get this into

> a

> > releasable state, up to and including taking on comaint of this

> module in

> > case you are busy/no longer interested in Perl development and/or > > maintaining this module -- but no pressure, it's totally fine if you

> don't

> > want to take that route, too! > > > > cc: modules@perl.org > > > > thanks, > > > > Karen Etheridge > > ether@cpan.org

> >

Tue Jun 11 16:49:52 2013 ether [...] cpan.org - Correspondence added

(resend, to fix bad cc) On 2013-06-10 14:50:41, ETHER wrote: Show quoted text

> It has been six weeks since my last ping, and I haven't heard from > you, since trying to reach you since March. > > This message is an official request to modules@perl.org to formally > adopt Log::Dispatch::File::Stamped so I can get the aforementioned > rewrites into the PAUSE index. > > (Log-Dispatch-File-Stamped-0.10_010 has been up for over a month, with > no failure reports.) > > > On 2013-04-22 14:39:47, ETHER wrote:

> > > > Log-Dispatch-File-Stamped-0.10_002 has been uploaded to PAUSE as an > > unauthorized release, as my $company is using it in its

> production

> > code now, but I'd really like this to get your blessing :) > > > > (cc modules@perl.org - this is the third attempt to contact you over

> a

> > span of a few months -- earlier attempts are when I filed this > > ticket, and when I inquired about a public repository and/or > > process for patching, via > > https://rt.cpan.org/Ticket/Display.html?id=84228) > > > > > > On Tue Apr 09 16:22:17 2013, ETHER wrote:

> > > > > > Log::Dispatch::File optionally does a number of nice things, like

> > bypassing

> > > block buffering, closing the filehandle after every write, etc

> that

> > this

> > > module does not handle. (From t/other_options.t in the below-

> > mentioned

> > > repository, the options that are currently not respected are:

> > autoflush,

> > > close_after_write, mode, and syswrite.) > > > > > > As I really would like to use timestamped files, but keep using

> the

> > > existing settings that I need in production, I've fixed this

> module

> > as well

> > > as made some modifications to Log::Dispatch::File itself to make > > > subclassing a little easier. > > > > > > Dave Rolsky has my fixes for Log::Dispatch::File at > > > https://github.com/karenetheridge/Log-

> > Dispatch/tree/topic/fix_subclassing.

> > > > > > I've rewritten ::File::Stamped to do the right thing in all cases,

> > as well

> > > as writing tests to confirm this, at > > > https://github.com/karenetheridge/Log-Dispatch-File-Stamped (using

> > the 0.10

> > > release as a starting point). > > > > > > I'm happy to do anything extra that is needed to help get this

> into

> > a

> > > releasable state, up to and including taking on comaint of this

> > module in

> > > case you are busy/no longer interested in Perl development and/or > > > maintaining this module -- but no pressure, it's totally fine if

> you

> > don't

> > > want to take that route, too! > > > > > > cc: modules@perl.org > > > > > > thanks, > > > > > > Karen Etheridge > > > ether@cpan.org

> > > >

> >

Sat Jun 15 12:11:02 2013 ether [...] cpan.org - Taken

Mon Jun 17 18:34:08 2013 ether [...] cpan.org - Correspondence added

fixed in v0.10_002 and v0.11

Mon Jun 17 18:34:08 2013 ether [...] cpan.org - Status changed from 'patched' to 'resolved'

Mon Jun 17 18:34:08 2013 ether [...] cpan.org - Fixed in 0.10_002 added