Glenn Goodrich

@rstacruz I would say, just do it. Release it from your fork if needed. Clearly, @ejholmes has moved on from this gem.

I am pretty sure that pry-debugger requires C stuff too.

@bobbytables Could this be done with custom middleware?

Something like, erm, [this](https://github.com/Skookum/vulcan-cors) (see the README for caveats, but I think it's a decent start)

Hey @JulieFerrario can you invite me, too, please? [email protected]

FWIW, this issue just bit us in the rear. As a hack, I am overriding nil.extend to stop this from happening. Not sure it's necessarily an roar-rails issue, but it's...

Well, I am spitting out a message from my #extend, and I see: ``` [Server:server-one] ESC[0mESC[0m09:59:24,597 INFO [stdout] (http-/172.31.0.107:8080-3) **** Stop trying to extend nil, jerk Mail::RFC2822::Address0ESC[0m [Server:server-one] ESC[0mESC[0m09:59:24,608 INFO...

Actually, in our case, we may explicitly be calling player.extend(PlayerRepresenter) when player is nil (but we don't think it is) In other words, I think, in our case, this is...

Hit this problem too. FWIW, the following allows me to work: ``` gem "guard", "~>1.8.3" gem "guard-rspec" gem "guard-jruby-rspec", github: 'jkutner/guard-jruby-rspec' ``` Hope that helps people use this gem until...