Skip Menu |

This queue is for tickets about the VMware-API-LabManager CPAN distribution.

Report information
The Basics
Id: 69478
Status: resolved
Priority: 0/
Queue: VMware-API-LabManager

People
Owner: bennie [...] cpan.org
Requestors: john [...] johnrbarker.com
Cc:
AdminCc:

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



CC: john [...] johnrbarker.com
Subject: Missing use Data:Debug for LabManager.pm
Date: Thu, 14 Jul 2011 16:48:16 +0100
To: bug-VMware-API-LabManager [...] rt.cpan.org
From: john [...] johnrbarker.com (John Barker)
Hi, VMware/API/LabManager.pm Line 117 is: warn "\n\nERROR DETAILS:\n" . Dumper($data) if $self->{debug}; But LabManager.pm does not have a "use Data::Dumper;" line. This is only hit when running with $labman->config(debug => 1) Thanks, John Barker
CC: john [...] johnrbarker.com
Subject: Re: [rt.cpan.org #69478] Missing use Data:Debug for LabManager.pm
Date: Thu, 14 Jul 2011 18:56:18 -0700
To: bug-VMware-API-LabManager [...] rt.cpan.org
From: Phillip Pollard <phil [...] crescendo.net>
Thank you very much for catching this. I have updated the module and uploaded the corrected version to CPAN. It should be available shortly. I have also added your contact information in as a contributor to the module. Thank you for your time and effort in catching this. - Phil On Jul 14, 2011, at 9:36 AM, john via RT wrote: Show quoted text
> Thu Jul 14 12:36:55 2011: Request 69478 was acted upon. > Transaction: Ticket created by john@johnrbarker.com > Queue: VMware-API-LabManager > Subject: Missing use Data:Debug for LabManager.pm > Broken in: (no value) > Severity: (no value) > Owner: Nobody > Requestors: john@johnrbarker.com > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=69478 > > > > Hi, > > VMware/API/LabManager.pm Line 117 is: > warn "\n\nERROR DETAILS:\n" . Dumper($data) if $self->{debug}; > But LabManager.pm does not have a "use Data::Dumper;" line. > > This is only hit when running with $labman->config(debug => 1) > > Thanks, > John Barker > >
Apparently I forgot to close this ticket when I fixed it back in 2011. I've also noted the RT# in the Cange log of the module.