Skip Menu |

This queue is for tickets about the RT-Client-REST CPAN distribution.

Report information
The Basics
Id: 78937
Status: rejected
Priority: 0/
Queue: RT-Client-REST

People
Owner: jlmartinez [...] capside.com
Requestors: cvicente [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in:
  • 0.37
  • 0.43
Fixed in: (no value)



Subject: Incorrect dereference of return value from form_parse?
First of all, thank you for this very useful module. For some strange reason, this problem started happening today with 0.37. I upgraded to 0.43 but that did not help. See below for how I made it work: The problem: $ perl /tmp/test-rt.pl Can't use an undefined value as an ARRAY reference at /usr/lib/perl5/site_perl/5.8.8/RT/Client/REST.pm line 117. --- The code: use RT::Client::REST; use RT::Client::REST::Ticket; use strict; my $id = 449086; my $RT_SERVER = 'https://rt.mydomain.com'; my $RT_USER = 'xxxx'; my $RT_PASS = 'xxxx'; # Create RT object my $rt = RT::Client::REST->new(server => $RT_SERVER, timeout => 30, ); # Log into RT $rt->login(username=>$RT_USER, password=>$RT_PASS); my $ticket = RT::Client::REST::Ticket->new(rt => $rt, id => $id, )->retrieve; ---- The fix: --- REST.pm 2012-01-09 10:09:51.000000000 -0800 +++ REST.pm.new 2012-08-13 09:28:31.000000000 -0700 @@ -112,7 +112,7 @@ } my $form = form_parse($self->_submit("$type/$id")->decoded_content); - my ($c, $o, $k, $e) = @{$$form[0]}; + my ($c, $o, $k, $e) = @{$form->[0]}; if (!@$o && $c) { RT::Client::REST::Exception->_rt_content_to_exception($c)->throw;
Hello, Can you please provide more information about this bug? - Did this start to happen after an RT upgrade, Perl upgrade, or an upgrade of a module? - How is authentication into your RT handled? We can't apply the patch until we know the origin of this behaviour, because this is working for other users around the world.
Seems odd indeed. One thing to do is to test with 5.8.8, which seems to be the version of Perl used when the failure occurred. perlbrew? Or we can perhaps just close this, since the requestor did not reply to the posed questions. Who uses 5.8.8 nowadays anyway?
We can't figure out what the problem was and there is no way to reproduce it. Rejecting.