-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
NameError (uninitialized constant DeviseTokenAuth::Concerns::User::BCrypt) #333
Comments
I am having this issue aswell |
thanks @andersonbrandon |
@booleanbetrayal any plan to release new gem version? |
Would like to get a new gem version out in the next couple of days, but am waiting for one changeset to make it in. In the meantime, you could always point to master: gem 'devise_token_auth', :git => 'https://github.com/lynndylanhurley/devise_token_auth.git', :branch => 'master' |
ok, thanks!!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I get error when doing multiple API requests in my ROR application running this gem which is deployed on heroku using Puma (based on this article https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server). Especially the error occurs when I have set Puma parameter -w (defining number of workers) to amount bigger than 1. Interestingly the error does not occur when I have set parameter -t (number of threads) to amount biger than 1. So it is probably solely connected to web concurrency defined by puma workes. Please see below details of the error:
app[web.1]: NameError (uninitialized constant DeviseTokenAuth::Concerns::User::BCrypt):
app[web.1]: vendor/bundle/ruby/2.0.0/gems/devise_token_auth-0.1.30/app/models/devise_token_auth/concerns/user.rb:111:in
token_is_current?' app[web.1]: vendor/bundle/ruby/2.0.0/gems/devise_token_auth-0.1.30/app/models/devise_token_auth/concerns/user.rb:86:in
valid_token?'app[web.1]: vendor/bundle/ruby/2.0.0/gems/devise_token_auth-0.1.30/app/controllers/devise_token_auth/concerns/set_user_by_token.rb:40:in
set_user_by_token' app[web.1]: vendor/bundle/ruby/2.0.0/gems/devise_token_auth-0.1.30/lib/devise_token_auth/controllers/helpers.rb:115:in
current_user'app[web.1]: vendor/bundle/ruby/2.0.0/gems/devise_token_auth-0.1.30/lib/devise_token_auth/controllers/helpers.rb:103:in
authenticate_user!' app[web.1]: vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:424:in
block in make_lambda'app[web.1]: vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:143:in
call' app[web.1]: vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:143:in
block in halting_and_conditional'app[web.1]: vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in
call' app[web.1]: vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in
block in halting'app[web.1]: vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in
call' app[web.1]: vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in
block in halting'app[web.1]: vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in
call' app[web.1]: vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in
block in halting'app[web.1]: vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in
call' app[web.1]: vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in
run_callbacks'The text was updated successfully, but these errors were encountered: