-
Notifications
You must be signed in to change notification settings - Fork 859
SOLR-18347: Fix five Admin UI defects found by Selenium #4818
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
Open
NextbrickInc
wants to merge
4
commits into
apache:main
Choose a base branch
from
NextbrickInc:solr-18347-admin-ui
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
b9c899b
SOLR-18347: Guard null core selection in Admin UI
rayshrey e7e66a5
SOLR-18347: Fix remaining Admin UI defects
rayshrey aa5f588
Merge remote-tracking branch 'origin/main' into solr-18347-admin-ui
rayshrey 9b5545d
SOLR-18347: Handle every ping status explicitly in Core Overview
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| # See https://github.com/apache/solr/blob/main/dev-docs/changelog.adoc | ||
| title: Fix five Admin UI defects found by Selenium testing | ||
| type: fixed # added, changed, fixed, deprecated, removed, dependency_update, security, other | ||
| authors: | ||
| - name: Shrey Narayan | ||
| nick: NextbrickInc | ||
| links: | ||
| - name: SOLR-18347 | ||
| url: https://issues.apache.org/jira/browse/SOLR-18347 |
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
BTW, if there is a lot of flakiness in this test, I am getting closer to migrating the Admin UI to using the generated V2 Javascript client, which I think is more reliable. And honestly, I think i might have made some commits that may even have broke the
schema-designer.jsnow that I think of it (not sure), so it may be okay to not worry about this page... It's on my list to get to "done done'!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.
Thanks @epugh — two things that might change the calculus.
It isn't flaky any more. The
@AwaitsFixblamed "transient failures at automation speed"; thereal cause was deterministic. The designer addressed Luke by core name, and a core name only
resolves on the node hosting it — with
configureCluster(2), that's the wrong node about half thetime. Addressing the collection fixes it: 53 tests, 18 suites, 0 failures.
Your hunch is right.
SchemaDesignerResponse.corecame in with SOLR-18152 (#4203), commented"Active replica core name ... used for Luke API calls" — reasonable-looking, just not routable
from an arbitrary node. Nothing else in that migration looks affected; every Schema Designer
assertion passes on top of it.
So I'd keep the test rather than drop the page — it's what would have caught this. And the V2
client would issue the same request against the same core name, so this class of bug survives the
migration either way.
Status — I think this is ready to go in.
9b5545ddb4.tidyclean,PingRequestHandlerTest6/6.@janhoy — the only reservation you raised was the five-in-one packaging. If you're willing to take
it as-is, I'd appreciate an approval. If not, say so and I'll split it along
PingRequestHandler+ Core Overview vs. the four UI-only fixes today.@epugh — if the Schema Designer question above is settled for you, a second approval would let this
land.