-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
similar issue to #39 #50
Comments
Thanks, provide as much relevant info as possible and I'll revisit. |
log
framework trace
|
db config with a few details removed:
|
I can trigger it by putting in bogus credentials or taking one of my test databases down. Using v0.2.2 |
I'll setup a similar environment soon but can you try doing |
get similar error with
Also tried updating to rails 4.0.5 to see if that helped in any way, but no dice. Everything continues to work in 2.0.0-p353 and 1.9.3-p448. |
just to be clear: When running with ruby 2.1.0 and rails 4.0.3 or rails 4.0.5 |
i looks like got the same issue... |
@etherbob v0.3.0.rc1 is released. If that release fixes these issues please close the issue. If not, let me know. Thanks |
Rails 4.0.3 and Ruby 2.1.0 if I switch back to Ruby 2.0 or earlier it goes away. I will add more detail as I get it but wanted to let you know it's not an isolated issue.
The text was updated successfully, but these errors were encountered: