Thank you Drew.
> In any case this bug is really easy to replicate and I even found
> a related issue on the Ruby issue tracker here
> (http://redmine.ruby-lang.org/issues/show/1063) except that I am not on XP
> and this isn't 1.8.6 or 1.9.1.
1.8.7 inherits a lot of 1.8.6 code (both share the same codebase)
1.9.1 had the same issue for console devices (STDOUT and STDERR)
If you mention this didn't happen on previous version, then is a regression.
>
> This exact same line of code works fine on 1.8.7 p302, the previous stable
> for 187. As a result of this, I cannot use p330 with our in-house rails
> projects because requests just die. Any insight is greatly appreciated!
>
Understood. I'll try to replicate in all the available versions and
report back to Ruby-Core.
Thank you for your time posting this, is really helpful.
--
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry
I've reported the regression:
http://redmine.ruby-lang.org/issues/show/4293
And also indicated where in the code the break was introduced.
Assigned to Nobu for confirmation and possible thoughts about the fix.
Will keep you posted.
A real pleasure.
FYI, seems the issue got solved and a fix will be backported into
1.8.7 pretty soon.
I hope in a month or so a new patchlevel will go out.
Is pending to be backported to ruby_1_8_7 branch. As you can see is
assigned to Shyouhei Urabe, maintainer of the 1.8.7 release.
I've just updated the ticket with a ping to Urabe-san.
I don't want to step into other's roles at Core.