You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem happens for Ruby 2.1, 2.3 on my local machine.
Reproduce steps:
export BUNDLE_GEMFILE=$PWD/gemfiles/ar5.gemfile
export DB=sqlite
bundle install
bundle exec rake
I got the following error for the first time. But the error disappears for the second time.
Error: test: a has_one association where the association is created between model versions and then the associated is updated between model versions when reified should see the associated as it was at the time. (AssociationsTest): ActiveRecord::ConfigurationError: Association named 'version_associations' was not found on PaperTrail::Version; perhaps you misspelled it?
activerecord (3.2.22.2) lib/active_record/associations/join_dependency.rb:112:in build' activerecord (3.2.22.2) lib/active_record/associations/join_dependency.rb:123:inblock in build'
Any clues?
The text was updated successfully, but these errors were encountered:
This is a known issue. Ben and I have just been living with it. Since it only happens once per contributor, it has been a low priority, but we'd still love to fix it.
The problem happens for Ruby 2.1, 2.3 on my local machine.
Reproduce steps:
I got the following error for the first time. But the error disappears for the second time.
Error: test: a has_one association where the association is created between model versions and then the associated is updated between model versions when reified should see the associated as it was at the time. (AssociationsTest): ActiveRecord::ConfigurationError: Association named 'version_associations' was not found on PaperTrail::Version; perhaps you misspelled it?
activerecord (3.2.22.2) lib/active_record/associations/join_dependency.rb:112:in
build' activerecord (3.2.22.2) lib/active_record/associations/join_dependency.rb:123:in
block in build'Any clues?
The text was updated successfully, but these errors were encountered: