NoMethodError: undefined method `params_encoder' Ruby 2.4.0 & faraday 0.14.0

[PrimeTimeTran]

Basic Info

• Faraday Version: 0.14.0
• Ruby Version: 2.4.0

Issue description

I'm expecting to be able to run Model.import(force: true) in the rails console and move forward with configuring my Elastic search using the elasticsearch-rails gem

This is the error/backtrace I get though.

NoMethodError: undefined method `params_encoder' for {"timeout"=>300, :proxy=>nil}:Hash
from /Users/Lois/.rvm/gems/ruby-2.4.0/gems/faraday-0.14.0/lib/faraday/request.rb:60:in `url'

Steps to reproduce:

1. Create new rails app
   rails new elasticrails

2. Add elastic-search gems:

gem 'elasticsearch-model', git: 'git://github.com/elastic/elasticsearch-rails.git', branch: 'master'
gem 'elasticsearch-rails', git: 'git://github.com/elastic/elasticsearch-rails.git', branch: 'master'

3. Bundle install:
   bundle install

4. Add model:
   rails g model Price price:integer

5. Setup db:
   rails db:create db:migrate

6. Include elastic-search-rails to model file:

# app/models/price.rb
class Price
  include Elasticsearch::Model
  include Elasticsearch::Model::Callbacks
  index_name([Rails.env,base_class.to_s.pluralize.underscore].join('_'))
...
end

7. Open rails console:
   rails console

8. Run import command:
   Price.import(force: true)

[iMacTia]

Hi @PrimeTimeTran,
thanks for the details but having also the full backtrace would help in this case rather than just the first line. I might notice the issue immediately with that, otherwise I'll need to setup the project following your steps, but that will take significantly longer.

[PrimeTimeTran]

Hey @iMacTia,
That is the entire trace.

[iMacTia]

OK! That’s strange...
I’ll try to replicate it then and see why that happens. However I’d suggest raising this also with the elasticsearch-model or elasticsearch-Rails maintainers as it might be due to the way they use Faraday internally

[PrimeTimeTran]

Yeah, I've already opened up an issue on elasticsearch-rails, but I don't know where in their gem it's getting called from so wasn't sure what else I could tell them that's useful.

Also thanks for looking into this~! We appreciate your work

[PrimeTimeTran]

I made a mistake. It has to do with the initializers I did in this blog post.
https://medium.com/@thecolorfulcrayon/configuring-elasticsearch-on-rails-8bcbe973e9e7

I'm closing this issue. My apologies. Thanks for your time.

[iMacTia]

No worries!
Thank you very much for the update.

[mattdrewitt]

For anyone who lands here from google, make sure to use deep_symbolize_keys when loading your config file as if they are mix and match you will see this problem.

[richessler]

@mattdrewitt thank you for this!