-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Painless: ensure type "UnmodifiableMap" for params #13885
Conversation
It's a user facing bug so removed |
❕ Gradle check result for 5851f44: UNSTABLE
Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #13885 +/- ##
============================================
+ Coverage 71.42% 71.61% +0.19%
- Complexity 59978 61315 +1337
============================================
Files 4985 5065 +80
Lines 282275 288124 +5849
Branches 40946 41719 +773
============================================
+ Hits 201603 206348 +4745
- Misses 63999 64776 +777
- Partials 16673 17000 +327 ☔ View full report in Codecov by Sentry. |
5851f44
to
6a01c54
Compare
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.
Could we add a yml test case to verify we can always get the expected behavior?
Hi. How can we specify number of nodes in the yml test? Also, how to send request to a specific node? I tried looking into the |
So the YAML client tests by default run with one node (if I am not mistaken) but the
Alternatively, you could use node selector instead, it would help you to always connect to right node:
|
84817c7
to
0df68f8
Compare
Signed-off-by: Rohit Ashiwal <rashiwal@amazon.com>
0df68f8
to
2973bb5
Compare
❌ Gradle check result for 0df68f8: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
modules/lang-painless/src/test/java/org/opensearch/painless/WhenThingsGoWrongTests.java
Show resolved
Hide resolved
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-13885-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 194005ebcaf79cf4f0f9fecd96d4b9e90ca9d1c0
# Push it to GitHub
git push --set-upstream origin backport/backport-13885-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x Then, create a pull request where the |
@r1walz Can you please backport manually? Appreciate it. |
…t#13885) Signed-off-by: Rohit Ashiwal <rashiwal@amazon.com>
…t#13885) Signed-off-by: Rohit Ashiwal <rashiwal@amazon.com>
…t#13885) Signed-off-by: Rohit Ashiwal <rashiwal@amazon.com>
…t#13885) (opensearch-project#13948) (cherry picked from commit 194005e) Signed-off-by: Rohit Ashiwal <rashiwal@amazon.com> Signed-off-by: kkewwei <kkewwei@163.com>
…t#13885) Signed-off-by: Rohit Ashiwal <rashiwal@amazon.com>
Description
See comment here: #10561 (comment)
Related Issues
Resolves #10561
Check List
New functionality includes testing.All tests passNew functionality has been documented.New functionality has javadoc addedAPI changes companion pull request created.Public documentation issue/PR createdBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.