fix(gnovm): correct OwnerID retrieval #3401
Closed
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.
When an object is persisted, the
owner
field is not saved along with it. As a result, when the object is restored, it does not have an associatedowner
, even though theOwnerID
field is available.This discrepancy can lead to side effects, such as failing to correctly retrieve the
owner
. Consequently, operations likemarkDirtyAncestors
do not function as expected.This PR addresses the issue by updating the
GetOwnerID
function to correctly handle this scenario.