2008/5/17 Leon Brocard [EMAIL PROTECTED]:
Thanks for the investigation Thomas, but I'd like to hold off until
someone actually fixes the real problems and quietens the warnings
using understanding.
Thanks to petdance, mst and dakkar, we finally have a working
Test::WWW::Mechanize::Catalyst:
Hi!
On Thu, May 15, 2008 at 10:20:23AM -0400, John Goulah wrote:
Since these fix tests, will these modules get patched and released
with this applied?
Hm, actually I only notified Leon about the patches. I will also submit
the patches directly to Andy (for WWW::Mechanize)
--
2008/5/15 John Goulah [EMAIL PROTECTED]:
Since these fix tests, will these modules get patched and released
with this applied?
Thanks for the investigation Thomas, but I'd like to hold off until
someone actually fixes the real problems and quietens the warnings
using understanding.
For now
Hi!
On Sun, May 11, 2008 at 07:10:27PM +0100, Leon Brocard wrote:
2008/5/10 Daniel McBrearty [EMAIL PROTECTED]:
I'd like Leon's opinion on this. Forwarding to him again.
I understand many bits of it but have given up trying to get it
working. I would love a patch which passes tests on
2008/5/10 Daniel McBrearty [EMAIL PROTECTED]:
I'd like Leon's opinion on this. Forwarding to him again.
I understand many bits of it but have given up trying to get it
working. I would love a patch which passes tests on both old and new
lib-www-perls.
Leon
I think there was some discussion over the same error in the POE HTTP
client over on perlmonks that included a this is the line of code that
is wrong. I can't find the link offhand though.
well, I see really three places to look at this:
1. in HTTP::Message - IMO the check on the content is
On Wed, May 07, 2008 at 10:51:37PM +0200, Daniel McBrearty wrote:
Not sure who that's pointed at Matt, but if you mean me, sorry for that.
No, I meant John and his soapbox.
In all honesty, if I could've worked out *what* needed fixing and
where, I would have done so. What I did was at least
Not sure who that's pointed at Matt, but if you mean me, sorry for that.
In all honesty, if I could've worked out *what* needed fixing and
where, I would have done so. What I did was at least try to indicate
to people where the error was coming from and why, and what they might
do temporarily in
On Mon, May 5, 2008 at 11:12 PM, Daniel McBrearty
[EMAIL PROTECTED] wrote:
If you don't want new versions of modules, then *don't upgrade them*.
and when you (or a total newcomer to the language/framework) do a
*new* install? and the latest greatest is broken right out of the
box? looks
On Mon, May 05, 2008 at 03:46:09PM -0500, Jonathan Rockway wrote:
* On Mon, May 05 2008, Daniel McBrearty wrote:
tht's reasonable.
what is not so reasonable is suddenly deciding that you are going to
*croak* on something which you didn't even test for with previous
releases.
A
If you don't want new versions of modules, then *don't upgrade them*.
and when you (or a total newcomer to the language/framework) do a
*new* install? and the latest greatest is broken right out of the
box? looks great, hey?
The code may have been broken - but not so broken that it couldn't
work
yeah, I started setting up cat on a new system yesterday and hit this :-(
The salient line seems to be :
HTTP::Message content not bytes at lib/Test/WWW/Mechanize/Catalyst.pm
line 88
I will spend an hour or two on it now, as I hate force installing, but
am starting almost from scratch and don't
OK, I walked through the code and found out roughly what is going on.
Hard to say where the real source of the bug is (could be at least two
modules) but I have a workaround which I am using (basically just to
remove the croak in HTTP::Message, a bit dirty but probably
harmless).
There was a recent SoPW on PerlMonks about this. Seems HTTP::Message is
doing the right thing.
http://perlmonks.org/?node_id=683833
-Ashley
On May 4, 2008, at 2:21 PM, Daniel McBrearty wrote:
OK, I walked through the code and found out roughly what is going on.
Hard to say where the real
14 matches
Mail list logo
