fix(projectOwnership): set new owner's usage storage correctly #5308
Conversation
This file contains 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
noliveleger
changed the base branch from
release/2.024.33
to
task-1302-sync-counter-lock-users
Base automatically changed from
task-1302-sync-counter-lock-users
to
release/2.024.33
November 27, 2024 19:04
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📣 Summary
Fixed an issue where the usage storage for the new owner was not updated correctly during project ownership transfers.
📖 Description
This PR addresses a bug in the project ownership transfer process where the new owner's usage storage was not being updated properly. As a result, storage allocations stayed the same for the previous owner, were not transferred to the new owner, and became inaccurate.
👀 Preview steps
2.024.33.cprevious owner and current owner storage counter are not updated (seeUserProfile.attachment_storage_bytes)💭 Notes
Previously, when storage counters became out-of-sync, the periodic task
sync_storage_counterswould eventually catch and correct the discrepancy.