[26927] in Perl-Users-Digest

home help back first fref pref prev next nref lref last post

Perl-Users Digest, Issue: 8899 Volume: 10

daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sun Jan 29 21:05:23 2006

Date: Sun, 29 Jan 2006 18:05:06 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)

Perl-Users Digest           Sun, 29 Jan 2006     Volume: 10 Number: 8899

Today's topics:
        Problem with search.cpan.org grep tool <jkeen_via_google@yahoo.com>
    Re: Problem with search.cpan.org grep tool <jkeen_via_google@yahoo.com>
    Re: When were @- and @+ added <sisyphus1@nomail.afraid.org>
    Re: When were @- and @+ added <rvtol+news@isolution.nl>
    Re: When were @- and @+ added <1usa@llenroc.ude.invalid>
    Re: When were @- and @+ added <sisyphus1@nomail.afraid.org>
    Re: When were @- and @+ added <sisyphus1@nomail.afraid.org>
    Re: When were @- and @+ added <1usa@llenroc.ude.invalid>
    Re: When were @- and @+ added <sisyphus1@nomail.afraid.org>
    Re: When were @- and @+ added <rvtol+news@isolution.nl>
        Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)

----------------------------------------------------------------------

Date: Mon, 30 Jan 2006 00:02:05 GMT
From: James E Keenan <jkeen_via_google@yahoo.com>
Subject: Problem with search.cpan.org grep tool
Message-Id: <1IcDf.838$OY4.514@trndny02>

I am encountering a problem using search.cpan.org's grep tool tonight to 
locate strings which I know to be found within particular distributions.

Example 1:  I go to http://search.cpan.org/tools/CPAN-1.83 and grep for 
'CPAN'.  Result:

### BEGIN ERROR MESSAGE ###
ERROR
The requested URL could not be retrieved

While trying to retrieve the URL: 
http://search.cpan.org:9290/grep?release=CPAN-1.83&string=CPAN&i=1&n=1

The following error was encountered:

     * Zero Sized Reply

Squid did not receive any data for this request.
### END ERROR MESSAGE ###

The string 'CPAN' obviously must be found somewhere within that 
distribution.

Example 2:  I go to 
http://search.cpan.org/grep?release=List-Compare-0.32&string=List&i=1&n=1 
and grep for 'list'.  I know that string exists in that module, because 
I wrote it!  Result:

### BEGIN ERROR MESSAGE ###
ERROR
The requested URL could not be retrieved

While trying to retrieve the URL: 
http://search.cpan.org:9290/grep?release=List-Compare-0.32&string=List&i=1&n=1 



The following error was encountered:

     * Zero Sized Reply

Squid did not receive any data for this request.
### END ERROR MESSAGE ###

Googling for "Zero Sized Reply" suggests that this is a server-side 
problem with Squid.  Are other people experiencing this?  Thanks.

Jim Keenan


------------------------------

Date: Mon, 30 Jan 2006 00:08:39 GMT
From: James E Keenan <jkeen_via_google@yahoo.com>
Subject: Re: Problem with search.cpan.org grep tool
Message-Id: <43DD5908.1030300@yahoo.com>

James E Keenan wrote:

> I am encountering a problem using search.cpan.org's grep tool tonight to 
> locate strings which I know to be found within particular distributions.
> 
>
> The following error was encountered:
> 
>     * Zero Sized Reply
> 
> Squid did not receive any data for this request.
> ### END ERROR MESSAGE ###
>
Here's an excerpt from Squid's FAQ 
(http://www.squid-cache.org/Doc/FAQ/FAQ_long.html):

11.51 Why do I sometimes get ``Zero Sized Reply''?

This happens when Squid makes a TCP connection to an origin server, but 
for some reason, the connection is closed before Squid reads any data. 
Depending on various factors, Squid may be able to retry the request 
again. If you see the ``Zero Sized Reply'' error message, it means that 
Squid was unable to retry, or that all retry attempts also failed.

What causes a connection to close prematurely? It could be a number of 
things, including:
	1 	An overloaded origin server.
	2 	TCP implementation/interoperability bugs. See the  System-Dependent 
Weirdnesses section for details.
	3 	Race conditions with HTTP persistent connections.
	4 	Buggy or misconfigured NAT boxes, firewalls, and load-balancers.
	5 	Denial of service attacks.
	6 	Utilizing  TCP blackholing on FreeBSD.

You may be able to use tcpdump to track down and observe the problem.

Jim Keenan


------------------------------

Date: Mon, 30 Jan 2006 10:07:24 +1100
From: "Sisyphus" <sisyphus1@nomail.afraid.org>
Subject: Re: When were @- and @+ added
Message-Id: <43dd4b3b$0$21414$afc38c87@news.optusnet.com.au>


"A. Sinan Unur" <1usa@llenroc.ude.invalid> wrote in message
news:Xns975A62FF45729asu1cornelledu@127.0.0.1...
> "Sisyphus" <sisyphus1@nomail.afraid.org> wrote in
> news:43dc85d3$0$5922$afc38c87@news.optusnet.com.au:
>
> > ActiveState's build 815 seems immune to the problem.
> > However, their build 810 (perl 5.8.4) *does* suffer this strange
> > affliction, as does my MinGW-built perl 5.8.7, and my VC++7.0-built
> > perl 5.8.7. I'll wait and see what perl 5.8.8 brings.
>
> Are these all on the same machine?
>

Yes - on the same Windows 2000 box.
I'm wondering whether build 815 incorporates a patch that addresses this
isuue. With ActiveState perl, 'perl -V' lists the patches that have been
applied, but I can't see anything listed there (see below) that looks like
it might have fixed this particular problem. Of course, the fix might have
been applied in build 814 or 813 ... but I don't know how to find out which
patches were applied to those builds (unless I actually install those 2
builds and run 'perl -V' :-)

I'll make some further enquiries on the perl-win32-users list hosted by
ActiveState. Someone there might be able to point me to more definitive
information.

Here are the patches listed for build 815:

  Locally applied patches:
        ActivePerl Build 815 [211909]
        Iin_load_module moved for compatibility with build 806
        PerlEx support in CGI::Carp
        Less verbose ExtUtils::Install and Pod::Find
        instmodsh upgraded from ExtUtils-MakeMaker-6.25
        Patch for CAN-2005-0448 from Debian with modifications
        Upgrade to Time-HiRes-1.76
        25774 Keys of %INC always use forward slashes
        25747 Accidental interpolation of $@ in Pod::Html
        25362 File::Path::mkpath resets errno
        25181 Incorrect (X)HTML generated by Pod::Html
        24999 Avoid redefinition warning for MinGW
        24699 ICMP_UNREACHABLE handling in Net::Ping
        21540 Fix backward-compatibility issues in if.pm

Cheers,
Rob




------------------------------

Date: Sun, 29 Jan 2006 23:32:38 +0100
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: When were @- and @+ added
Message-Id: <drjk77.1a8.1@news.isolution.nl>

Dr.Ruud schreef:
> Abigail schreef:
>> Sisyphus:
> 
>>>  use warnings;
>>>  "foo" =~ /o/g;
>>>  print scalar @-;
>>> 
>>>  If I don't 'use warnings;' in that script, it reverts to
>>> outputting '1'.
>> 
>> I can't reproduce that with any version of Perl that supports @-.
> 
> perl, v5.8.6 built for i386-freebsd-64int
> 
> $ perl -e 'use strict; use warnings; "foo" =~ /o/g; print scalar @-'
> 134641065
> $ perl -e 'use warnings; "foo" =~ /o/g; print scalar @-'
> 134621613
> $ perl -e '"foo" =~ /o/g; print scalar @-'
> 1


perl, v5.8.7 built for cygwin-thread-multi-64int

$ perl -e 'use strict; use warnings; "foo" =~ /o/g; print scalar @-'
1628668893
$ perl -e 'use warnings; "foo" =~ /o/g; print scalar @-'
35
$ perl -e '"foo" =~ /o/g; print scalar @-'
1


perl, v5.8.7 built for MSWin32-x86-multi-thread (ActivePerl build 815)

C:\>perl -e "use strict; use warnings; 'foo' =~ /o/g; print scalar @-"
27651977
C:\>perl -e "use warnings; 'foo' =~ /o/g; print scalar @-"
786437
C:\>perl -e "'foo' =~ /o/g; print scalar @-"
1

-- 
Affijn, Ruud

"Gewoon is een tijger."


------------------------------

Date: Sun, 29 Jan 2006 23:51:05 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: When were @- and @+ added
Message-Id: <Xns975ABFD8D3695asu1cornelledu@127.0.0.1>

"Sisyphus" <sisyphus1@nomail.afraid.org> wrote in
news:43dd4b3b$0$21414$afc38c87@news.optusnet.com.au: 

> 
> "A. Sinan Unur" <1usa@llenroc.ude.invalid> wrote in message
> news:Xns975A62FF45729asu1cornelledu@127.0.0.1...
>> "Sisyphus" <sisyphus1@nomail.afraid.org> wrote in
>> news:43dc85d3$0$5922$afc38c87@news.optusnet.com.au:
>>
>> > ActiveState's build 815 seems immune to the problem.
>> > However, their build 810 (perl 5.8.4) *does* suffer this strange
>> > affliction, as does my MinGW-built perl 5.8.7, and my VC++7.0-built
>> > perl 5.8.7. I'll wait and see what perl 5.8.8 brings.
>>
>> Are these all on the same machine?
>>
> 
> Yes - on the same Windows 2000 box.
> I'm wondering whether build 815 incorporates a patch that addresses
> this isuue. With ActiveState perl, 'perl -V' lists the patches that
> have been applied, but I can't see anything listed there (see below)
> that looks like it might have fixed this particular problem. Of
> course, the fix might have been applied in build 814 or 813 ... but I
> don't know how to find out which patches were applied to those builds
> (unless I actually install those 2 builds and run 'perl -V' :-)

http://aspn.activestate.com/ASPN/docs/ActivePerl/5.8/changes-58.html

Hope this helps.

Sinan
-- 
A. Sinan Unur <1usa@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)

comp.lang.perl.misc guidelines on the WWW:
http://mail.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html



------------------------------

Date: Mon, 30 Jan 2006 11:17:14 +1100
From: "Sisyphus" <sisyphus1@nomail.afraid.org>
Subject: Re: When were @- and @+ added
Message-Id: <43dd5b98$0$10626$afc38c87@news.optusnet.com.au>


"Dr.Ruud" <rvtol+news@isolution.nl>

>
>
> perl, v5.8.7 built for MSWin32-x86-multi-thread (ActivePerl build 815)
>
> C:\>perl -e "use strict; use warnings; 'foo' =~ /o/g; print scalar @-"
> 27651977
> C:\>perl -e "use warnings; 'foo' =~ /o/g; print scalar @-"
> 786437
> C:\>perl -e "'foo' =~ /o/g; print scalar @-"
> 1
>

Aaah, so AS build 815 *is* afflicted (I get the same) - but not in the same
way as my other builds. I'll file a bug report now.

Cheers,
Rob




------------------------------

Date: Mon, 30 Jan 2006 11:22:14 +1100
From: "Sisyphus" <sisyphus1@nomail.afraid.org>
Subject: Re: When were @- and @+ added
Message-Id: <43dd5cc4$0$11102$afc38c87@news.optusnet.com.au>


"A. Sinan Unur" <1usa@llenroc.ude.invalid>

>>  but I
> > don't know how to find out which patches were applied to those builds
> > (unless I actually install those 2 builds and run 'perl -V' :-)
>
> http://aspn.activestate.com/ASPN/docs/ActivePerl/5.8/changes-58.html
>

Thanks for the link (which I've saved). Couldn't really see anything that
would explain the change in behaviour.

Dr.Ruud has just pointed out that build 815 is afflicted - though in
not-quite-the-same-way as my other builds, so I'll file a bug report.

Cheers,
Rob




------------------------------

Date: Mon, 30 Jan 2006 00:38:23 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: When were @- and @+ added
Message-Id: <Xns975AC7DDCFE09asu1cornelledu@127.0.0.1>

"Sisyphus" <sisyphus1@nomail.afraid.org> wrote in
news:43dd5cc4$0$11102$afc38c87@news.optusnet.com.au: 

> 
> "A. Sinan Unur" <1usa@llenroc.ude.invalid>
> 
>>>  but I
>> > don't know how to find out which patches were applied to those
>> > builds (unless I actually install those 2 builds and run 'perl -V'
>> > :-) 
>>
>> http://aspn.activestate.com/ASPN/docs/ActivePerl/5.8/changes-58.html
>>
> 
> Thanks for the link (which I've saved). Couldn't really see anything
> that would explain the change in behaviour.
> 
> Dr.Ruud has just pointed out that build 815 is afflicted - though in
> not-quite-the-same-way as my other builds, so I'll file a bug report.

It is a little crazy ... I tried the cases he posted, and I get 
something different (with the same AS Perl):

C:\opt> perl -e "use warnings; 'foo' =~ /o/g; print scalar @-"
262152

C:\opt> perl -e "use strict; use warnings; 'foo' =~ /o/g; print scalar 
@-"
1

C:\opt> perl -e "'foo' =~ /o/g; print scalar @-"
1

Anyway, a bug report is probably the best way to go at this point.

Thank you.

Sinan
-- 
A. Sinan Unur <1usa@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)

comp.lang.perl.misc guidelines on the WWW:
http://mail.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html


------------------------------

Date: Mon, 30 Jan 2006 12:07:02 +1100
From: "Sisyphus" <sisyphus1@nomail.afraid.org>
Subject: Re: When were @- and @+ added
Message-Id: <43dd6745$0$15127$afc38c87@news.optusnet.com.au>


"A. Sinan Unur" <1usa@llenroc.ude.invalid> wrote in message

>
> Anyway, a bug report is probably the best way to go at this point.
>

For anyone interested, the perlbug auto-reply informs me that my ticket has
been assigned an ID of [perl #38363].

Cheers,
Rob




------------------------------

Date: Mon, 30 Jan 2006 02:20:21 +0100
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: When were @- and @+ added
Message-Id: <drjt6m.do.1@news.isolution.nl>

Sisyphus schreef:

> Aaah, so AS build 815 *is* afflicted [...]
> I'll file a bug report now.

OK, thanks.

-- 
Affijn, Ruud

"Gewoon is een tijger."


------------------------------

Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin) 
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>


Administrivia:

#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc.  For subscription or unsubscription requests, send
#the single line:
#
#	subscribe perl-users
#or:
#	unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.  

NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice. 

To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.

#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.

#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.


------------------------------
End of Perl-Users Digest V10 Issue 8899
***************************************


home help back first fref pref prev next nref lref last post