Seeing "already initialized constant" with respect to JSON about manageiq-schema

[jrafanie]

log the caller of version.rb:4, 5, 6, 7, 8, etc...

Maybe there's a fine detail difference in how it's being required...

[Fryguy]

This happens on Ruby 2.3 as well

[Fryguy]

@jrafanie Thoughts?

[jrafanie]

Such as require vs. require_relative or require with FQ path vs. relative, etc.

[Fryguy]

Figured it out. So, I noticed this happened specifically with rake spec:migrations:complete_up and rake spec:migrations:complete_down. Those are suspicious because they shell out to another rake task, then wait for that subprocess to complete. However, all they do in the subprocess is a bundle exec rake db:migrate. So, I tried running just that, and I don't get the warnings. This led me to conclude that is not the rake task, but the act of shelling out. Then, I remembered ye olde Bundle.with_clean_env, and this worked. Bundler somehow messes with the env causing rake to use the pure stdlib json, but activerecord to use the json gem.

[jrafanie]

Bundler somehow messes with the env causing rake to use the pure stdlib json, but activerecord to use the json gem.

Wow, yuck but cool!