Skip to content

Bump reactor-netty from 1.2.4 to 1.2.5 and reactor from 3.5.20 to 3.7.5 #18243

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

Merged
merged 1 commit into from
May 9, 2025

Conversation

reta
Copy link
Contributor

@reta reta commented May 9, 2025

Description

Bump reactor-netty from 1.2.4 to 1.2.5 and reactor from 3.5.20 to 3.7.5

Related Issues

N/A

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By 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.

@reta reta requested a review from a team as a code owner May 9, 2025 00:50
@reta reta added dependencies Pull requests that update a dependency file backport 3.0 labels May 9, 2025
Copy link
Contributor

github-actions bot commented May 9, 2025

❌ Gradle check result for 0e123af: 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?

@reta reta force-pushed the update.reactor branch from 0e123af to 5492771 Compare May 9, 2025 01:19
Copy link
Contributor

github-actions bot commented May 9, 2025

❌ Gradle check result for 5492771: 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?

Copy link
Contributor

github-actions bot commented May 9, 2025

❌ Gradle check result for 5492771: 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?

Copy link
Contributor

github-actions bot commented May 9, 2025

❌ Gradle check result for 5492771: 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?

Copy link
Contributor

github-actions bot commented May 9, 2025

✅ Gradle check result for 5492771: SUCCESS

Copy link

codecov bot commented May 9, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.51%. Comparing base (560ac10) to head (5492771).
Report is 15 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #18243      +/-   ##
============================================
- Coverage     72.56%   72.51%   -0.06%     
- Complexity    67261    67293      +32     
============================================
  Files          5476     5482       +6     
  Lines        310478   310676     +198     
  Branches      45133    45155      +22     
============================================
- Hits         225313   225282      -31     
- Misses        66840    67060     +220     
- Partials      18325    18334       +9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@reta reta merged commit c060f92 into opensearch-project:main May 9, 2025
30 checks passed
@opensearch-trigger-bot
Copy link
Contributor

The backport to 3.0 failed:

The process '/usr/bin/git' failed with exit code 128

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-3.0 3.0
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-3.0
# Create a new branch
git switch --create backport/backport-18243-to-3.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c060f92b6d5ee4fb6f6c92aa1912d34e6d5dfe91
# Push it to GitHub
git push --set-upstream origin backport/backport-18243-to-3.0
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-3.0

Then, create a pull request where the base branch is 3.0 and the compare/head branch is backport/backport-18243-to-3.0.

reta added a commit to reta/OpenSearch that referenced this pull request May 9, 2025
reta added a commit that referenced this pull request May 10, 2025
….5 (#18243) (#18249)

(cherry picked from commit c060f92)

Signed-off-by: Andriy Redko <[email protected]>
neuenfeldttj pushed a commit to neuenfeldttj/OpenSearch that referenced this pull request Jun 26, 2025
neuenfeldttj pushed a commit to neuenfeldttj/OpenSearch that referenced this pull request Jun 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 3.0 backport-failed dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants