-
Notifications
You must be signed in to change notification settings - Fork 60
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
uninitialized constant Capistrano::Slack::Faraday #29
Comments
Don't know if it's the same issue, but 1.3.2 doesn't seem to post to our Slack room, while 1.3.1 does. |
thanks for the report will take a look. for now lock to 1.3.1 |
I'm getting this error as well with v1.3.2. |
Getting same error |
Can't lock to 1.3.1: |
I got same problem today and this fix works for me:
Good luck |
I have the same problem :-( |
and then bundle |
The problem is here capistrano-slack/lib/capistrano/slack.rb Line 73 in d806534
|
@ant-workaholic For me it wasn't enough to pin to 1.3.1, I had to delete 1.3.2 before I could post to slack again. |
what capistrano version do you have? |
I'm running capistrano 2.15.5 |
Facing the same issue with capistrano 2.15.5 and capistrano-slack 1.3.1 & 1.3.2 |
While upgrading our application to Rails 4 we ran into this error:
Other gems in our application rely on Faraday, but capistrano-slack doesn't, so it's understandable that this error would occur since Faraday hasn't actually been loaded.
The text was updated successfully, but these errors were encountered: