Bug 755903 - Use of uninitialized value in string eq at .. FormFu/Constraint.pm line 107
Summary: Use of uninitialized value in string eq at .. FormFu/Constraint.pm line 107
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-HTML-FormFu
Version: 16
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Iain Arnell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-22 11:17 UTC by Daniel Piddock
Modified: 2013-01-23 12:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-23 12:40:17 UTC
Type: ---


Attachments (Terms of Use)
Make the noise stop in FormFu::Constraint (825 bytes, patch)
2011-11-22 11:17 UTC, Daniel Piddock
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
CPAN 72611 0 None None None Never

Description Daniel Piddock 2011-11-22 11:17:46 UTC
Created attachment 534999 [details]
Make the noise stop in FormFu::Constraint

Description of problem:
"Use of uninitialized value in string eq at /usr/share/perl5/vendor_perl/HTML/FormFu/Constraint.pm line 107."

Version-Release number of selected component (if applicable):
0.09003-2.fc16

How reproducible:
Certain input data causes the warning to be generated

Steps to Reproduce:
1.
2.
3.
  
Actual results:
"Use of uninitialized value in string eq at /usr/share/perl5/vendor_perl/HTML/FormFu/Constraint.pm line 107." printed to terminal

Expected results:
Glorious silence

Additional info:
Scalar::Util's reftype can return undef. There is no sanity check before using in a string eq, hence terminal spam.

Comment 1 Iain Arnell 2011-11-22 12:36:40 UTC
I've reported the problem upstream with a slightly modified patch.

Comment 2 Fedora End Of Life 2013-01-16 22:45:50 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Jan Pazdziora 2013-01-17 09:05:43 UTC
(In reply to comment #0)
> Created attachment 534999 [details]
> Make the noise stop in FormFu::Constraint
> 
> Description of problem:
> "Use of uninitialized value in string eq at
> /usr/share/perl5/vendor_perl/HTML/FormFu/Constraint.pm line 107."
> 
> Version-Release number of selected component (if applicable):
> 0.09003-2.fc16
> 
> How reproducible:
> Certain input data causes the warning to be generated
> 
> Steps to Reproduce:
> 1.
> 2.
> 3.
>   
> Actual results:
> "Use of uninitialized value in string eq at
> /usr/share/perl5/vendor_perl/HTML/FormFu/Constraint.pm line 107." printed to
> terminal

What's the code you are using (what is the reproducer)? There is no "use warnings" in that Constraint.pm.

Comment 4 Daniel Piddock 2013-01-22 14:12:32 UTC
The code is part of a Catalyst project. I've gone back to it and cannot reproduce the warning messages using the current 0.09007-1.fc16 so I can't figure out a smaller test case.

Comment 5 Iain Arnell 2013-01-23 12:40:17 UTC
Upstream never closed the bug report, but the fix is present in 0.09007.


Note You need to log in before you can comment on or make changes to this bug.