-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugfix synchronization collisions with database when the object entry already exists #241
Conversation
Code Climate has analyzed commit 3576cab and detected 2 issues on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 66.3% (0.5% change). View more on Code Climate. |
Signed-off-by: Jeremy Ho <jujaga@gmail.com>
The searchObjects service call had a structural change that was not propagating correctly to the synchronization methods. This commit fixes that by ensuring that the values are extracted out correctly from the new structure. Also improved test branch coverage and JSDocs. Signed-off-by: Jeremy Ho <jujaga@gmail.com>
…licy Signed-off-by: Jeremy Ho <jujaga@gmail.com>
6417271
to
3576cab
Compare
key: 'key', | ||
userId: SYSTEM_USER, | ||
permissions: false | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldnt the pagination query params be in here?
Description
Synchronization was attempting to perform an insertion operation when the object already exists and collides with the database. It was not going down the right branch of sync code.
Synchronization does not work at this time for objects that already exist in COMS, and will impact clients' ability to retrieve up to date statuses of their S3 buckets.
SHOWCASE-3498
SHOWCASE-3503
Types of changes
Bug fix (non-breaking change which fixes an issue)
Breaking change (fix or feature that would cause existing functionality to change)
Checklist
Further comments