Skip Menu |

This queue is for tickets about the Device-LaCrosse-WS23xx CPAN distribution.

Report information
The Basics
Id: 63826
Status: open
Priority: 0/
Queue: Device-LaCrosse-WS23xx

People
Owner: cpanrt [...] edsantiago.com
Requestors: jeremy [...] austux.net
Cc:
AdminCc:

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



Subject: eval( _time_convert($BCD) ) died: wu-upload.pl: Internal error: bad datetime '0'
Date: Sat, 11 Dec 2010 23:38:55 +1100
To: bug-Device-LaCrosse-WS23xx [...] rt.cpan.org
From: Jeremy Lunn <jeremy [...] austux.net>
I am using the generic weather underground upload script at: http://www.wunderground.com/windowsinstall/wu-upload.pl (though this error comes from Device::LaCrosse::WS23xx). Received this error for a while after reconnecting my console. wu-upload.pl: eval( _time_convert($BCD) ) died: wu-upload.pl: Internal error: bad datetime '0' at /usr/local/lib/perl/5.10.1/Device/LaCrosse/WS23xx.pm line 251. at /home/jeremy/bin/wu-upload.pl line 129 Happy to supply more details if it happens again. perl, v5.10.1 (*) built for i486-linux-gnu-thread-multi
Show quoted text
> Received this error for a while after reconnecting my console. > wu-upload.pl: eval( _time_convert($BCD) ) died: wu-upload.pl: Internal > error: bad datetime '0' at > /usr/local/lib/perl/5.10.1/Device/LaCrosse/WS23xx.pm line 251. > at /home/jeremy/bin/wu-upload.pl line 129
Sorry about that. By "reconnecting your console", do you mean that something happened and your WSxxxx console got reset? If so, I'm wondering if this happened while reading a daily max/min timestamp that hadn't yet been initialized. Show quoted text
> Happy to supply more details if it happens again.
Does that mean it is no longer happening? In other words: do you need an immediate fix? If it's still happening, this might help me track it down: 1) Change WS23xx.pm line 251 from 'die' to 'croak' 2) setenv PERL5OPT=MCarp=verbose 3) rerun your script 4) post the stacktrace result here (eg by replying to this email) I no longer have a WS23xx unit -- mine died in August -- but I'll see if I can find a way to handle this condition better.
Device::LaCrosse::WS23xx v0.07 is now on CPAN. It might take a while (a day?) for it to get indexed and to propagate. This version has slightly better error handling for the condition you describe: it might give more info, and it will return 0 (the epoch) instead of die()ing.
Subject: Re: [rt.cpan.org #63826] eval( _time_convert($BCD) ) died: wu-upload.pl: Internal error: bad datetime '0'
Date: Sun, 12 Dec 2010 16:57:14 +1100
To: bug-Device-LaCrosse-WS23xx [...] rt.cpan.org
From: Jeremy Lunn <jeremy [...] austux.net>
On 12/12/2010, at 3:59 AM, Eduardo Santiago Munoz via RT wrote: Show quoted text
> Sorry about that. By "reconnecting your console", do you mean that > something happened and your WSxxxx console got reset?
Yep, it was disconnected from power for a little while. Show quoted text
> If so, I'm > wondering if this happened while reading a daily max/min timestamp that > hadn't yet been initialized.
Quite possible. Show quoted text
>> Happy to supply more details if it happens again.
> > Does that mean it is no longer happening? In other words: do you need > an immediate fix?
Pretty much. I just thought it was worth reporting the bug. It's pretty minor if it only occurs for a short while after the console has been reset. Though potentially frustrating if you don't know why it's not working at that time. Thanks, I'll let you know if it reoccurs. Jeremy