Setter sometimes doesn't update the changes, and therefore, doesn't save later on. about rails HOT 4 OPEN

Can you reproduce this bug on Rails 7.1? Rails 6.1 isn't supported anymore

from rails.

Well, since I have a hard time reproducing it, it would mean upgrading the platform, which will take some time.
But if I find an easy way to reproduce I'll try on the latest version.

from rails.

A little bit of update, I have trouble reproducing it on a small project, but I have been able te debug it a bit more.

When calling reload on an activeRecord model, I start to have different instances of AttributeSet, and only one of them is updated when using the setter. Therefore, the object changes method returns empty, and the save doesn't send any update query, as it expects nothing has changed.
After calling a save, things are going back to normal (i.e the same AttributeSet on both places), and changes are tracked appropriately.

object.send(:mutations_from_database).instance_variable_get(:@attributes).to_s
#<ActiveModel::LazyAttributeSet:0x0000000111c8af70>
object.instance_variable_get(:@attributes).to_s
#<ActiveModel::LazyAttributeSet:0x00000001124caa00>

Given that there have been very little changes there between 6.1 and 7.1, I suspect the bug is still present.

How could I track more what happens during a reload on those objects?

from rails.

Search for def reload. You will find methods like this

from rails.