uninitialized constant Capistrano::Slack::Faraday

[seanlinsley]

While upgrading our application to Rails 4 we ran into this error:

capistrano-slack-35112edc71d3/lib/capistrano/slack.rb:73:in `rescue in block (3 levels) in extended': uninitialized constant Capistrano::Slack::Faraday (NameError)
  from capistrano-slack-35112edc71d3/lib/capistrano/slack.rb:66:in `block (3 levels) in extended'
  from capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `instance_eval'
  from capistrano-2.15.5/lib/capistrano/configuration/execution.rb:138:in `invoke_task_directly'

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.

[seanlinsley]

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.

[j-mcnally]

thanks for the report will take a look. for now lock to 1.3.1

[jstayton]

I'm getting this error as well with v1.3.2.

[gakshay]

Getting same error

[wagnerpereira]

Can't lock to 1.3.1: Could not find gem 'capistrano-slack (= 1.3.1) ruby' in https://github.com/j-mcnally/capistrano-slack.git (at master). Source contains 'capistrano-slack' at: 1.3.2

[rusllonrails]

I got same problem today and this fix works for me:

 gem 'capistrano-slack', '1.3.1'

Good luck

[ant-workaholic]

I have the same problem :-(

[rusllonrails]

@ant-workaholic

gem 'capistrano-slack', '1.3.1'

and then bundle doesn't fix it?

[ebeigarts]

The problem is here https://github.com/j-mcnally/capistrano-slack/blob/d806534fe96ab7f835dd007389d05a17e373024b/lib/capistrano/slack.rb#L73

[lefthand]

@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.

[WouterSchoofs]

what capistrano version do you have?

[lefthand]

I'm running capistrano 2.15.5

[rdsoze]

Facing the same issue with capistrano 2.15.5 and capistrano-slack 1.3.1 & 1.3.2