Skip Menu |

This queue is for tickets about the Net-ThreeScale-Client CPAN distribution.

Report information
The Basics
Id: 103074
Status: resolved
Priority: 0/
Queue: Net-ThreeScale-Client

People
Owner: DLAMBLEY [...] cpan.org
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 2.0.2
Fixed in:
  • 2.1.1
  • 2.1.2
  • 2.1.3



Subject: Possible hash randomization problems in test suite
See http://matrix.cpantesters.org/?dist=Net-ThreeScale-Client%202.0.2 for a pass/fail overview --- there are random fail reports mainly for perl5.18 and newer, which indicates a hash randomization problem somewhere.
On Tue Mar 24 16:30:01 2015, SREZIC wrote: Show quoted text
> See http://matrix.cpantesters.org/?dist=Net-ThreeScale-Client%202.0.2 > for a pass/fail overview --- there are random fail reports mainly for > perl5.18 and newer, which indicates a hash randomization problem > somewhere.
I can reproduce this issue with 5.18.2. The attached patch should fix the problem with t/02_format_transactions.t. Best regards, Dave Lambley
Subject: 0001-Fix-for-Perl-5.18.2.patch
From 99d3964e2f5c1d4a5f93e53815f79551a4e708ba Mon Sep 17 00:00:00 2001 From: Dave Lambley <dave@adzuna.com> Date: Wed, 22 Apr 2015 12:02:09 +0100 Subject: [PATCH] Fix for Perl 5.18.2. --- lib/Net/ThreeScale/Client.pm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lib/Net/ThreeScale/Client.pm b/lib/Net/ThreeScale/Client.pm index d6a6af7..e680a19 100644 --- a/lib/Net/ThreeScale/Client.pm +++ b/lib/Net/ThreeScale/Client.pm @@ -279,7 +279,8 @@ sub _format_transactions { $output .= $pref . "[app_id]=" . $trans->{app_id}; - while (my ($k, $v) = each(%{$trans->{usage}})) { + foreach my $k (sort keys %{$trans->{usage}}) { + my $v = $trans->{usage}->{$k}; $k = uri_escape($k); $v = uri_escape($v); $output .= "&"; -- 1.9.1
This is still broken. Any chance of a new release? I'd be happy to help.
On Fri Nov 27 09:22:19 2015, KAORU wrote: Show quoted text
> This is still broken. Any chance of a new release? I'd be happy to help.
This is fixed in an unofficial release, 2.1.2.
Fixed officially in 2.1.3.