[uss_qualifier] Fix notification index checks - #1651
Merged
barroco merged 3 commits intoAug 20, 2026
Conversation
barroco
approved these changes
Aug 20, 2026
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 PR removes uss_qualifier checks that overly constrain DSS implementation beyond what the requirements they are based on actually require. Specifically, this PR targets the expectation that the initial notification_index value should be 0 as this is not supported by the associated requirements.
This partially addresses #1650. I tested the new behavior by adding the lines below to test_docker_fully_mocked.sh (what is used in the CI to run monitoring tests), but that change cannot be directly included in this PR as this PR does not fully resolve #1650 so some checks still fail in that configuration.