fix: Incorrect evaluation if object was initialized#179
Merged
Conversation
St4NNi
approved these changes
Jun 18, 2024
Member
St4NNi
left a comment
St4NNi
left a comment
There was a problem hiding this comment.
Good catch, somehow this was missed during testing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This addresses a bug in the
put_objectprocess where the system incorrectly evaluated whether an updated object was initialized which leads to an error when the system tries to create a duplicate of the already existing object after the upload.Impact
This fix ensures that the system accurately tracks whether a new object has been initialized on update through the data proxy's S3 interface and does not erroneously attempt to create a duplicate.