-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Avoid un-intended wildcard matches in ProfileIntegTests
#117888
Merged
elasticsearchmachine
merged 4 commits into
elastic:main
from
n1v0lg:fix-suggest-profiles-it
Dec 5, 2024
Merged
Avoid un-intended wildcard matches in ProfileIntegTests
#117888
elasticsearchmachine
merged 4 commits into
elastic:main
from
n1v0lg:fix-suggest-profiles-it
Dec 5, 2024
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
n1v0lg
added
>test
Issues or PRs that are addressing/adding tests
auto-backport
Automatically create backport pull requests when merged
:Security/Profile
User Profiles & Personalisation
v9.0.0
v8.16.2
v8.17.1
v8.18.0
labels
Dec 3, 2024
n1v0lg
changed the title
Fix
Avoid un-intended wildcard matches in Dec 3, 2024
ProfileIntegTests
test setup to avoid wildcard matchesProfileIntegTests
Pinging @elastic/es-security (Team:Security) |
slobodanadamovic
approved these changes
Dec 3, 2024
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.
LGTM
n1v0lg
added
the
auto-merge-without-approval
Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!)
label
Dec 4, 2024
This was referenced Dec 5, 2024
n1v0lg
added a commit
to n1v0lg/elasticsearch
that referenced
this pull request
Dec 5, 2024
The test setup for `ProfileIntegTests` is flawed, where the full name of a user can be a substring of other profile names (e.g., `SER` is a substring of `User <random-string>-space1`) -- when that's passed into suggest call with the `*` space, we get a match on all profiles, instead of only the one profile expected in the test, since we are matching on e.g. `SER*`. This PR restricts the setup to avoid the wildcard profile for that particular test. Closes: elastic#117782
n1v0lg
added a commit
to n1v0lg/elasticsearch
that referenced
this pull request
Dec 5, 2024
The test setup for `ProfileIntegTests` is flawed, where the full name of a user can be a substring of other profile names (e.g., `SER` is a substring of `User <random-string>-space1`) -- when that's passed into suggest call with the `*` space, we get a match on all profiles, instead of only the one profile expected in the test, since we are matching on e.g. `SER*`. This PR restricts the setup to avoid the wildcard profile for that particular test. Closes: elastic#117782
n1v0lg
added a commit
to n1v0lg/elasticsearch
that referenced
this pull request
Dec 5, 2024
The test setup for `ProfileIntegTests` is flawed, where the full name of a user can be a substring of other profile names (e.g., `SER` is a substring of `User <random-string>-space1`) -- when that's passed into suggest call with the `*` space, we get a match on all profiles, instead of only the one profile expected in the test, since we are matching on e.g. `SER*`. This PR restricts the setup to avoid the wildcard profile for that particular test. Closes: elastic#117782
elasticsearchmachine
pushed a commit
that referenced
this pull request
Dec 5, 2024
The test setup for `ProfileIntegTests` is flawed, where the full name of a user can be a substring of other profile names (e.g., `SER` is a substring of `User <random-string>-space1`) -- when that's passed into suggest call with the `*` space, we get a match on all profiles, instead of only the one profile expected in the test, since we are matching on e.g. `SER*`. This PR restricts the setup to avoid the wildcard profile for that particular test. Closes: #117782
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-backport
Automatically create backport pull requests when merged
auto-merge-without-approval
Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!)
:Security/Profile
User Profiles & Personalisation
Team:Security
Meta label for security team
>test
Issues or PRs that are addressing/adding tests
v8.16.2
v8.17.1
v8.18.0
v9.0.0
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.
The test setup for
ProfileIntegTests
is flawed, where the full name of a user can be a substring of other profile names (e.g.,SER
is a substring ofUser <random-string>-space1
) -- when that's passed into suggest call with the*
space, we get a match on all profiles, instead of only the one profile expected in the test, since we are matching on e.g.SER*
. This PR restricts the setup to avoid the wildcard profile for that particular test.Closes: #117782