Bug #106569 for Catalyst-Controller-WrapCGI: Module fails to seek($body,0,0)

Thu Aug 20 17:24:33 2015 perl [...] evancarroll.com - Ticket created

Subject:

Module fails to seek($body,0,0)

Find more information on http://stackoverflow.com/q/32128269/124486 Suggestion.. 1. Add the line to seek($body, 0,0 ) on StackOverflow. 2. Come up with a suggestion/convention to read from the body, and reset BEFORE-ONLY, or BEFORE-AND-AFTER you gobble $c->req->body. This is currently done ad-hoc but ALL of the Action::Deserialize's that I've checked just seek($body,0,0) before and do not reset the cursor when they're done.. (Though I find that ugly, and careless when we're transparently installing something via `sub begin`) -- Evan Carroll System Lord of the Internets http://www.evancarroll.com

Mon Nov 30 04:47:49 2015 perl [...] evancarroll.com - Correspondence added

On Thu Aug 20 16:24:33 2015, ECARROLL wrote: Show quoted text

> Find more information on http://stackoverflow.com/q/32128269/124486 > > Suggestion.. > 1. Add the line to seek($body, 0,0 ) on StackOverflow. > 2. Come up with a suggestion/convention to read from the body, and > reset BEFORE-ONLY, or BEFORE-AND-AFTER you gobble $c->req->body. This > is currently done ad-hoc but ALL of the Action::Deserialize's that > I've checked just seek($body,0,0) before and do not reset the cursor > when they're done.. (Though I find that ugly, and careless when we're > transparently installing something via `sub begin`)

If this bug doesn't get fixed, I'll be forced to fork this week and C:C:WrapCGI:ButMaintained will be on the way. -- Evan Carroll System Lord of the Internets http://www.evancarroll.com

Mon Nov 30 05:09:36 2015 rkitover [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #106569] Module fails to seek($body,0,0)
Date:	Mon, 30 Nov 2015 05:09:19 -0500
To:	bug-catalyst-controller-wrapcgi [...] rt.cpan.org
From:	Rafael Kitover <rkitover [...] gmail.com>

On November 30, 2015 at 4:47:56 AM, Evan Carroll via RT (bug-catalyst-controller-wrapcgi@rt.cpan.org) wrote: Queue: Catalyst-Controller-WrapCGI Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=106569 > On Thu Aug 20 16:24:33 2015, ECARROLL wrote: Show quoted text

> Find more information on http://stackoverflow.com/q/32128269/124486 > > Suggestion.. > 1. Add the line to seek($body, 0,0 ) on StackOverflow. > 2. Come up with a suggestion/convention to read from the body, and > reset BEFORE-ONLY, or BEFORE-AND-AFTER you gobble $c->req->body. This > is currently done ad-hoc but ALL of the Action::Deserialize's that > I've checked just seek($body,0,0) before and do not reset the cursor > when they're done.. (Though I find that ugly, and careless when we're > transparently installing something via `sub begin`)

If this bug doesn't get fixed, I'll be forced to fork this week and C:C:WrapCGI:ButMaintained will be on the way. Sorry Evan, I will fix it now. Why do you still bother with perl and the abusive asshole perl scum? I personally only touch this shit when I have to now. Fuck these people.

Mon Nov 30 05:09:38 2015 The RT System itself - Status changed from 'new' to 'open'

Mon Nov 30 14:07:35 2015 ether [...] cpan.org - Correspondence added

On 2015-11-30 02:09:36, rkitover@gmail.com wrote: Show quoted text

> Why do you still bother with perl and the abusive asshole perl scum? I > personally only touch this shit when I have to now. > > Fuck these people.

I've found, when dealing with projects that are entirely voluntary and unpaid, that I get out what I put in. The less abusive I am, the more helpful others are to me. Just a thought.

Mon Nov 30 16:34:29 2015 rkitover [...] cpan.org - Correspondence added

It's fixed with a test, and converted to dzil and all the test warnings fixed, and now on my github here: https://github.com/rkitover/catalyst-controller-wrapcgi

Mon Nov 30 16:34:32 2015 rkitover [...] cpan.org - Status changed from 'open' to 'resolved'

Mon Nov 30 16:34:32 2015 rkitover [...] cpan.org - Fixed in 0.035 added

Mon Nov 30 18:10:46 2015 perl [...] evancarroll.com - Correspondence added

On Mon Nov 30 15:34:29 2015, RKITOVER wrote: Show quoted text

> It's fixed with a test, and converted to dzil and all the test > warnings fixed, and now on my github here: > > https://github.com/rkitover/catalyst-controller-wrapcgi

Thanks. You rock. I don't mind doing the work. It takes 5 min to fork on CPAN and get it up to Github. I debugged the problem myself. I do mind however, having a bug request go 6 months without input and having to debug the same problem again because I forgot about it. Don't want to maintain the distro? Release it for others to maintain! Easy solution. When it takes more work to actually write a ticket on RT than to fork on CPAN, it's precisely because others don't want to be "abusive" of the system that they post first. Yea, I'm eerked. Twice I operated with good faith and debugged my own problem and rolled my own solution. Now, I want to see the breaks put down so I can be sure I don't have to do it for a third time. -- Evan Carroll System Lord of the Internets http://www.evancarroll.com

Tue Dec 01 03:14:41 2015 rkitover [...] cpan.org - Correspondence added

On Mon Nov 30 18:10:46 2015, ECARROLL wrote: Show quoted text

> On Mon Nov 30 15:34:29 2015, RKITOVER wrote:

> > It's fixed with a test, and converted to dzil and all the test > > warnings fixed, and now on my github here: > > > > https://github.com/rkitover/catalyst-controller-wrapcgi

> > Thanks. You rock. I don't mind doing the work. It takes 5 min to fork > on CPAN and get it up to Github. I debugged the problem myself. I do > mind however, having a bug request go 6 months without input and > having to debug the same problem again because I forgot about it. > Don't want to maintain the distro? Release it for others to maintain! > Easy solution. When it takes more work to actually write a ticket on > RT than to fork on CPAN, it's precisely because others don't want to > be "abusive" of the system that they post first. > > Yea, I'm eerked. Twice I operated with good faith and debugged my own > problem and rolled my own solution. Now, I want to see the breaks put > down so I can be sure I don't have to do it for a third time.

Yeah, I didn't fix this sooner because I have a lot of serious problems in life as you well know. I haven't been able to do much work on most of my projects the last few months. I'm usually much more attentive about fixing bugs, especially minor ones. The abusive assholes I was talking about are mst etc., don't tell me you haven't had problems with them yourself. Anyway, I'm a lot more careful about who I will work with on what now, and preferrably work on my own projects, it's not like there isn't a lot of stuff to work on on the internet that I need to tolerate pieces of shit like mst and his fan club. Message me on irc and I'll tell you about what he did to one of my projects, if you're interested. There is no one to maintain much of anything, perl is pretty dead. I don't even have perms on this module, but I added you as a committer on the github repo, if you want to do work on it just email me to do a release. Some of my modules these people forked without even having the courtesy of telling me that they wanted to do work on them or tell me what they were doing. Seriously fucking rude, but that's most of these pieces of shit. Like, it's hard to send an email or something? Anyway, I highly recommend you learn some languages people actually use, if you haven't already, like python, ruby, Scala, etc.. Python is a joy to work with, and it actually has enough strictness by default to support serious projects and is very easy to learn when you know Perl already. Up to you of course.

Tue Dec 01 04:27:30 2015 perl [...] evancarroll.com - Correspondence added

Show quoted text

> Yeah, I didn't fix this sooner because I have a lot of serious > problems in life as you well know. I haven't been able to do much work > on most of my projects the last few months. I'm usually much more > attentive about fixing bugs, especially minor ones. > > The abusive assholes I was talking about are mst etc., don't tell me > you haven't had problems with them yourself. Anyway, I'm a lot more > careful about who I will work with on what now, and preferrably work > on my own projects, it's not like there isn't a lot of stuff to work > on on the internet that I need to tolerate pieces of shit like mst and > his fan club. Message me on irc and I'll tell you about what he did to > one of my projects, if you're interested. > > There is no one to maintain much of anything, perl is pretty dead. I > don't even have perms on this module, but I added you as a committer > on the github repo, if you want to do work on it just email me to do a > release. > > Some of my modules these people forked without even having the > courtesy of telling me that they wanted to do work on them or tell me > what they were doing. Seriously fucking rude, but that's most of these > pieces of shit. Like, it's hard to send an email or something? > > Anyway, I highly recommend you learn some languages people actually > use, if you haven't already, like python, ruby, Scala, etc.. Python > is a joy to work with, and it actually has enough strictness by > default to support serious projects and is very easy to learn when you > know Perl already. Up to you of course.

dzuil is not my choice of build tool, but I'll be glad to help. Fuck mst with an iron spoon. I can honestly say he did more to push me away from Perl than any technological element. In fact, on tech meets he's a joke. I'm on a Perl team moving over to node. Our two biggest complaints are mst, and POE in that order. I've had extensive experience with python, and ruby. I think if I move to another language it'll be Haskell or Go. But, I'm still loving node. While I hate the language (ECMA5), the community, the fast pace of change, and the acceptance to new ideas has forged a climate that makes work fun again. Good luck in your future pursuits. -- Evan Carroll System Lord of the Internets http://www.evancarroll.com P.S. Fuck mst.