Skip to content

Conversation

willyborankin
Copy link
Contributor

Description

Bump log4j2 from 2.21.0 to 2.25.1

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.

@willyborankin willyborankin force-pushed the bump-log4j2 branch 2 times, most recently from e7aa42e to 82a7e2e Compare August 29, 2025 19:00
Copy link
Contributor

❌ Gradle check result for 82a7e2e: 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

❌ Gradle check result for 78e7fdf: 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 Sep 1, 2025

❌ Gradle check result for 928fa14: 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 Sep 2, 2025

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

@willyborankin willyborankin force-pushed the bump-log4j2 branch 2 times, most recently from db27748 to 6d1cdd1 Compare September 2, 2025 15:22
Copy link
Contributor

github-actions bot commented Sep 2, 2025

❌ Gradle check result for 6d1cdd1: 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 Sep 2, 2025

❌ Gradle check result for 5422987: 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 Sep 5, 2025

❌ Gradle check result for 06db206: 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 Sep 5, 2025

❌ Gradle check result for 0cd8253: 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 Sep 5, 2025

❌ Gradle check result for 897a611: 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 Sep 5, 2025

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

@willyborankin willyborankin force-pushed the bump-log4j2 branch 2 times, most recently from ca5c631 to 6e1510e Compare September 5, 2025 21:04
Copy link
Contributor

github-actions bot commented Sep 5, 2025

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

@willyborankin willyborankin marked this pull request as ready for review September 5, 2025 23:28
@willyborankin willyborankin requested a review from a team as a code owner September 5, 2025 23:28
Copy link
Contributor

github-actions bot commented Sep 6, 2025

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

❌ Gradle check result for 275c093: 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

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

✅ Gradle check result for c5d6e27: SUCCESS

Copy link

codecov bot commented Sep 15, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.92%. Comparing base (10f8c8e) to head (c30f407).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #19184      +/-   ##
============================================
+ Coverage     72.85%   72.92%   +0.07%     
- Complexity    69794    69816      +22     
============================================
  Files          5673     5673              
  Lines        320711   320754      +43     
  Branches      46360    46369       +9     
============================================
+ Hits         233642   233922     +280     
+ Misses        68143    67863     -280     
- Partials      18926    18969      +43     

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

Copy link
Contributor

✅ Gradle check result for afb6306: SUCCESS

Copy link
Contributor

@msfroh msfroh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot @willyborankin! Just a couple of minor comments.

Signed-off-by: Andrey Pleskach <[email protected]>
Copy link
Contributor

✅ Gradle check result for c30f407: SUCCESS

supercsv = "2.4.0"
log4j = "2.21.0"
log4j = "2.25.1"
error_prone_annotations = "2.41.0"
Copy link
Contributor

@navneet1v navneet1v Sep 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a reason for upgrading error_prone_annotations to 2.41.0 version when guava 33.2.1-jre brings in 2.26.1 ?

Due to this mismatch, now plugins like k-NN who uses guava has to remove error_prone_annotations so that there is no jar hell

jainankitk pushed a commit to jainankitk/OpenSearch that referenced this pull request Sep 22, 2025
jainankitk pushed a commit to jainankitk/OpenSearch that referenced this pull request Sep 22, 2025
jainankitk pushed a commit to jainankitk/OpenSearch that referenced this pull request Sep 22, 2025
asimmahmood1 pushed a commit to jainankitk/OpenSearch that referenced this pull request Sep 23, 2025
pranikum pushed a commit to pranikum/OpenSearch that referenced this pull request Sep 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants