-
Notifications
You must be signed in to change notification settings - Fork 131
[6.18.z] Add test case verifiying capsule sync in presence of null facet #20540
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
Merged
Gauravtalreja1
merged 1 commit into
6.18.z
from
cherry-pick-6.18.z-fb45d399431c51bae0da6bc185878f79c020aca6
Dec 22, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
issue (testing): The test does not explicitly verify that the subscription/content facet is actually null before triggering the capsule sync.
The test currently assumes unregister leaves a null subscription/content facet but never verifies it. To better cover SAT-39794/SAT-40496, please re-fetch the host after
unregister, and add an assertion that the subscription/content facet (or the specific UUID field involved in the bug) is null before callingcontent_sync. This will make the test a more reliable regression guard for unregister behavior.