However, in this case, nokogiri-1.10.9 gem was actually found. The jets deploy normally stops when native gems are not found. RE: Any way to get an advance notification of a problem like this, or catch this in the deploy process so it can rollback before affecting the application?īummer! Thanks for reporting. "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:72:in `require'" "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:72:in `require'", "/var/task/handlers/controllers/orders_controller.rb:1:in `'", "/var/runtime/gems/bundler-2.1.4/lib/bundler/runtime.rb:101:in `block in definition_method'", "/var/runtime/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in `requested_specs'", "/var/runtime/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `materialize'", "/var/runtime/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in `block in materialize'", "errorMessage": "Could not find nokogiri-1.10.9 in any of the sources", I recall that there was something special about native compiled gems like nokogiri.Īny way to get an advance notification of a problem like this, or catch this in the deploy process so it can rollback before affecting the application? Init error when loading handler handlers/controllers/orders_controller.create It looks like 1.10.9 is only a couple days old.
I fixed it by pinning nokogiri to 1.10.8 and re-bundling. I didn’t notice this right away because it crashes too early for the error to be sent to my error reporting app (Rollbar). Weird, because the gem installed fine locally and the deploy succeeded without errors. I did a bundle update jets recently and re-deployed my Jets app, and this error started happening on all functions.
0 kommentar(er)
