Skip to content

ObjectId already set #288

Answered by Bios-Marcel
Bios-Marcel asked this question in Q&A
Discussion options

You must be logged in to vote

So, it appears that this was an issue caused by serialising an object that was previously copied via ObjectCopier. The object in question contained the mentioned Lazy field.

Manually "copying" the field by calling the setter (which creates a fresh Lazy-reference) did the job!

Hope this helps anyone

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by Bios-Marcel
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant