I've tried to apply patch agains the 1.1.0.pre (the patch which broke it is in 1.1.0.pre as well). I have Mac OS X and tested on Ruby 1.9.1 and 1.8.7.
The problem is that in 1.9.1 on OSX cluster workers doesn't even start to listen and the whole cluster looks dead. Not that this would be caused by the patch. On 1.8.7 I've managed to run the cluster and applied the patch however the patch didn't fixed the problem. I still don't get anything from the background threads. Can you guys share your system configuration when the patch fixes the problem, please. On Jan 6, 8:45 pm, Gary Yngve <[email protected]> wrote: > Jonah, done. > > Sadly I don't have the time to invest to figure out how to write a > unit test for this.. seems tricky. > > I think it's scary that the passenger change was introduced without > realizing that it broke clusters, and it would be good to avoid a > repeat. > When a CEO has to weigh the benefits of a sexy web framework that > makes engg happy vs. the risk that new versions of the framework may > break in unpredictable ways that require engineering manhours or > impact customers, it is going to be a tough sell. > > -Gary > > On Jan 6, 1:31 am, jonah honeyman <[email protected]> wrote: > > > > > Gary, > > > Can you submit the patch to lighthouse? I would like to see this merged in > > to master and 1.0.x ASAP. I also think that a 1.0.16 release with this > > applied is more than appropriate. -- You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/merb?hl=en.
