RubyFlow Working Again: Sorry for the Issues
I upgraded Rubyflow to Rails 2.3.2 yesterday (to take advantage of a new feature) and even though everything seemed okay, the server had an old version of Rack and this caused some sporadic, nasty features that caused issues with posting comments and items (but not all the time!). Turns out it’s called the “Rails 2.3 params” issue and relates to having a pre-1.0 version of Rack installed. So.. now fixed :) Be aware of this if you upgrade your own apps.. (Update: Turns out to be something far more insidious.. a Rack 1.0 vs Passenger bug.. see in the thread for details.)
Anyway, RubyFlow also has a new feature. See those posts with a little crown and a red highlight? Those are “featured” posts that I’m marking off as being particularly noteworthy (often because I want to mention them on Ruby Inside). The leaderboard page has also gotten a little upgrade.
Comments
After upgrading to Rack 1.0, all was well.. then a few hours later RubyFlow was totally down with an error involving Rack::Lock.. except Rack::Lock only came with Rack 1.0 that was released today and I don’t use it!! WTF?!
xyz.. testing again..
For reference, the new error is: undefined method `new’ for “Rack::Lock”:String
Quite why new is being called on a string, I don’t know.
Trying Rails 2.3.2.1 downloaded directly - hopefully that will solve it :)
It seems that, potentially, the real Rack 1.0 is not working in the same way as the ersatz Rack 1.0 that comes with Rails 2.3.2 :)
Despite all of that, it happened again! Only restarting Apache got it to work again. I wonder why it only occurs after a few hours.. perhaps Passenger is reverting to a different Rack at some point, or…??!
Removing Rack 1.0 (real Gem version released today). Let’s see if that helps..
Aha. It appears to have been reported to Phusion as a bug:
http://code.google.com/p/phusion-passenger/issues/detail?id=279&colspec=ID%20Type%20Status%20Priority%20Milestone%20Stars%20Summary
Also see http://groups.google.com/group/rack-devel/browse_thread/thread/928e13477dcb459a
Post a comment