s P5L[ȤN0K0YARB*)I&x86_64-linux>  ?4"="44"="444"="444"="444"="44"="4 47     ' 0 9 B KT ]c s$8( 8( 8 ( 8 (8 ( 8( t9 $ 7' (]M& ( u    4! 4!47    &&")(  #] ) u >   ?.7*  * q  .7+e +  .7, ,  .7- - 11.7-AYYY1   !"#$%&'() E /home/slice-d5/.rvm/gems/ruby-2.5.1/gems/shoulda-matchers-3.1.2/lib/shoulda/matchers/active_model/allow_value_matcher/attribute_changed_value_error.rbE 
E E E E E "  " ! $ & E messageE The E  matcher attempted to set :E  on E  to E 6, but when the attribute was read back, it had stored E V instead. This creates a problem because it means that the model is behaving in a way that is interfering with the test -- there's a mismatch between the test that you wrote and test that we actually ran. There are a couple of reasons why this could be happening: * ActiveRecord is typecasting the incoming value. * The writer method for :E  has been overridden so that incoming values are changed in some way. If this exception makes sense to you and you wish to bypass it, try adding the `ignoring_interference_by_writer` qualifier onto the end of your matcher. If the test still does not pass after that, then you may need to do something different. If you need help, feel free to ask a question on the shoulda-matchers issues list: http://github.com/thoughtbot/shoulda-matchers/issues  E  successful? E ShouldaE MatchersE  ActiveModelE AllowValueMatcherE ErrorE AttributeChangedValueErrorE  matcher_nameE to_sE attribute_nameE modelE nameE  value_writtenE inspectE  value_readE  word_wrapE  attr_accessorE core#define_methodG}'?W 6Rq7Ph