getting a "can't modify frozen Gem::Version" RuntimeError with 4.1.0 in production only #605
Description
We have an app that is getting this error thrown, in production only, in this line
Started POST "/user_sessions/initialize_system" for 192.168.32.86 at 2018-05-18 16:44:26 -0700
Processing by UserSessionsController#initialize_system as HTML
Parameters: {"utf8"=>"✓", "authenticity_token"=>"7gVY+sMt9p/IlIM6eeFikwXEUR6NgeFg/VeNbLGyYi802yyxT+D+5d+UXog7syXdeAm+jAmadFaCAOQt4FIWYA==", "username"=>"admin", "password"=>"[FILTERED]", "password_confirmation"=>"[FILTERED]", "commit"=>"Create"}
Completed 500 Internal Server Error in 15ms (ActiveRecord: 2.1ms)
RuntimeError (can't modify frozen Gem::Version):
app/controllers/user_sessions_controller.rb:101:in `initialize_system'
The app automatically tries to login an initial user after initializing things.
We are just in the process of upgrading our gems to the latest and this came up as one of the last few issues we're facing.
We have seen #591 and looks very similar, however, that appears to be fixed a little bit ago in 4.0.1.
We cannot reproduce this in development mode. Because our app is somewhat unconventional (it's a web interface for a linux system and it interacts with the system functions a lot).
Any suggestions on how to debug (or even trace) this further?
ruby 2.4.3p205 (2017-12-14 revision 61247) [x86_64-linux]
authlogic (4.1.0)
rails (5.1.6)