Duplicate the context hash when duplicating an Attacher #653
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We hit an issue following the upgrade to 3.5.0 where
context[:record]
in anAttacher#finalize
call was set to an unpersisted duplicate of the record we were saving. This turned out to be because another part of our model save flow was duplicating the model for its own purposes and thecontext
hash was shared between the original attacher and its duplicate.The changes in fc6a3ed added a call to
attacher_copy.set_entity(self, name) if attacher_copy
. Because@context
in both attachers point at the same object, this ends up withcontext[:record]
for both records pointing to the new duplicate model.