Backport of [secrets sync] remove incorrect dom assertion into release/1.16.x #26132
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
hc-github-team-secure-vault-core
force-pushed
the
backport/ui/hotfix-client-counts-overview-test/socially-free-hermit
branch
from
fbfb624
to
d8e168e
Compare
github-actions
bot
added
the
hashicorp-contributed-pr
noelledaley
approved these changes
Mar 23, 2024
|
Build Results: |
|
CI Results: |
noelledaley
deleted the
backport/ui/hotfix-client-counts-overview-test/socially-free-hermit
branch
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.
Backport
This PR is auto-generated from #26131 to be assessed for backporting due to the inclusion of the label backport/1.16.x.
The below text is copied from the body of the original PR.
Removes a test failure caused by an incorrect assertion.
@hellobontempo and I paired on this and we believe the error is occurring because client activity data is generated as the test suite runs other acceptance tests. This correctly caused the
<UsageStats />component not to render (since there was activity data).Next up we should rewrite the test to stub the activity response to return 0 clients. That way we're ensuring that we can consistently predict the Vault cluster's client activity.
Overview of commits