Skip to content
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

Hadoop: make libjfs singleton to avoid possible jnr weakhashmap infinity loop #4407

Merged
merged 1 commit into from
Feb 18, 2024

Conversation

tangyoupeng
Copy link
Contributor

@tangyoupeng tangyoupeng commented Feb 18, 2024

No description provided.

Copy link

codecov bot commented Feb 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (3c69a0d) 56.06% compared to head (3eed5ae) 56.05%.

❗ Current head 3eed5ae differs from pull request most recent head b6fd3b5. Consider uploading reports for the commit b6fd3b5 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4407      +/-   ##
==========================================
- Coverage   56.06%   56.05%   -0.01%     
==========================================
  Files         154      154              
  Lines       40072    40072              
==========================================
- Hits        22465    22462       -3     
- Misses      15098    15100       +2     
- Partials     2509     2510       +1     

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

@tangyoupeng tangyoupeng changed the title Hadoop: make libjfs singleton to avoid possible jnr weakhashmap infin… Hadoop: make libjfs singleton to avoid possible jnr weakhashmap infinity loop Feb 18, 2024
@davies davies merged commit 38f279a into main Feb 18, 2024
26 of 27 checks passed
@davies davies deleted the libjfs_singleton branch February 18, 2024 08:22
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.

2 participants