Do we know what needs to be done?
I'm facing this in a fresh new app (Hobo 2.2.5 Rails 4.2.6), and if it is
easy, maybe I can work on a fix for Hobo, instead of just locally working
around the bug in my application.
2016. január 21., csütörtök 22:35:52 UTC+1 időpontban Ignacio Huerta a
Thanks for the confirmation Ed. We'll try to make Hobo compatible with
the latest responders as soon as possible.
Warm regards,
Ignacio
El 20-01-2016 a las 20:55, Ed Gomolka escribió:
> Ignacio:
> Thanks for the update.
> I read the Github thread, and experimented with the responders version
>
Ignacio:
Thanks for the update.
I read the Github thread, and experimented with the responders version in
my Gemfile as suggested by Stefan. I got exactly the outcome that he
described:
Responders version 2.1.0 works.
Responders version 2.1.1 fails (unless I add the line "public :render" to
Hi Ed,
We are investigating. There are some interesting thoughts in this Github
issue, including a test app, to see if you can reproduce:
https://github.com/Hobo/hobo/issues/176
Warm regards,
Ignacio
El 14-01-2016 a las 22:51, Ed Gomolka escribió:
> Hi Ignacio:
> I assume that this is some sort
Hmmm.. I've just encountered this as well in a app after an update of other
gems, including Hobo, to hobo 2.2.4, Downgraded to Hobo 2.2.3 and *still*
have the error.
This is on Rails 4.2.4 with Ruby 2.1.4p265.
So, I don't think it's Hobo.
Continuing to investigate.
Tim
On Tuesday, January
Hi Ed,
This is a strange error, I have not seen it before. It sounds like some
kind of version conflict. Can you share a small example app to reproduce it?
Thanks,
Ignacio
El 08-01-2016 a las 22:28, Ed Gomolka escribió:
> I recently upgraded to Hobo 2.2.4. I now get errors in all my
>
