Comments on: Rails Metal + Thin = no ‘each’ for String?

By: Joshaven

Joshaven — Wed, 07 Jul 2010 03:49:26 +0000

Thank you. I was having a similar problem and because of you didn’t have to debug for two hours.

I was getting a Time object rather then a string… with Sinatra + Thin

By: Lory Coloma

Lory Coloma — Wed, 20 Jan 2010 00:44:21 +0000

-You can’t really put it any more straightforward than that.

By: M. E. Patterson

M. E. Patterson — Mon, 18 Jan 2010 15:03:32 +0000

Yeah, that was what I thought at first, except I dug into the Thin code and discovered that they have a line:

if @body.is_a?(String)

and then they just yield the whole string instead of trying to break it into chunks. The other half of the if-else seems to expect that the @body is something that is actually enumerable and yields that back in chunks.

What I discovered (maybe something new in ActionController 2.3.5?) is that this ActionController BodyWrapper thing gets wrapped around my result, which, because it’s not a String object, makes it fall through to the else and kaboom. So it’s clear that the Thin guys had attempted to account for 1.9, but I guess something new in ActionController invalidated their fix. But by turning my plain string into an Array, it made the enumerating part of the else statement enumerate the single element and then it yields it perfectly. Was easier/more pleasant to make a tiny fix to my code than to hack up Thin.

By: Tweets that mention Rails Metal + Thin = no ‘each’ for String? « me, Patterson -- Topsy.com

Mon, 18 Jan 2010 12:25:44 +0000

[...] This post was mentioned on Twitter by Nicholas, Matt E. Patterson. Matt E. Patterson said: RT @mepatterson Rails Metal + Thin = no ‘each’ for String? « me, Patterson http://tinyurl.com/ybeaxgq [...]

By: ncancelliere

ncancelliere — Mon, 18 Jan 2010 12:15:38 +0000

In Ruby 1.9 String is no longer an enumerable using each(). You can check out this blog post which goes into details about the changes: http://blog.grayproductions.net/articles/ruby_19s_string

This is probably one of the bigger changes done in Ruby 1.9 … and I’m guessing Webrick is doing something to work around this, but maybe Thin hasn’t updated to 1.9 yet??