-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[grid]: Capabilities prefix starts with se:slotMatcher for DefaultSlotMatcher decision #14583
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
Conversation
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨Explore these optional code suggestions:
|
CI Failure Feedback 🧐(Checks updated until commit 0973487)
✨ CI feedback usage guide:The CI feedback tool (
In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:
where Configuration options
See more information about the |
…tMatcher decision Signed-off-by: Viet Nguyen Duc <[email protected]>
deb369a
to
0973487
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## trunk #14583 +/- ##
==========================================
- Coverage 58.48% 57.78% -0.70%
==========================================
Files 86 89 +3
Lines 5270 5609 +339
Branches 220 245 +25
==========================================
+ Hits 3082 3241 +159
- Misses 1968 2123 +155
- Partials 220 245 +25 ☔ View full report in Codecov by Sentry. |
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.
I don't think this is needed. I checked the existing code in the DefaultSlotMatcher
and it should be working. I will ask more question in the linked issue.
I am closing this PR, since this implementation is redundant. |
Thanks for contributing to Selenium!
A PR well described will help maintainers to quickly review and merge it
Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, help reviewers by making them as simple and short as possible.
Description
Motivation and Context
Fixes #14576
Grid supports Setting custom capabilities for matching specific Nodes.
However, recently, this feat hasn't worked anymore. It could be due to a few capabilities (e.g:
networkname:applicationName
,nodename:applicationName
) getting filtered (not meeting standards or something else) before coming to DefaultSlotMatcher.Via a fix recently #14323. All caps that start with the prefix
se:
are retained in the session response.Cap name contains
se:
is generic for many purposes, and those are also excluded in slot matcher decision as current implementation.So, to make the feat custom caps for matching specific Nodes works, we will dedicate a prefix
se:slotMatcher
, for any cap name starts with this prefix will be used in DefaultSlotMatcher decision.Also, it could be similar to #14323, adding an end-to-end test for this is tricky.
Types of changes
Checklist