[Don't Merge] Merge master branch into HDDS-10685#10754
Merged
Conversation
…cies. (apache#10399). Co-authored-by: Gargi Jaiswal <134698352+Gargi-jais11@users.noreply.github.com>
…ving tests in TestReconTaskControllerImpl (apache#10452)
…s in TestOMRatisSnapshots (apache#10453)
…ng DN report processing gaps in Recon. (apache#10326)
…THY IN_SERVICE datanode selection. (apache#10457).
…0409) Co-authored-by: Sreeja Chintalapati <schintalapati@Sreejas-MacBook-Pro.local>
…e blocks command (apache#10733) Co-authored-by: Siyao Meng <50227127+smengcl@users.noreply.github.com>
…snapshot diff (apache#10603) Co-authored-by: Wei-Chiu Chuang <jojochuang@gmail.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Gargi-jais11
marked this pull request as ready for review
July 14, 2026 07:13
Gargi-jais11
marked this pull request as draft
July 14, 2026 09:43
Gargi-jais11
force-pushed
the
HDDS-10685
branch
2 times, most recently
from
July 14, 2026 10:38
ce55e9c to
ab0074e
Compare
Gargi-jais11
marked this pull request as ready for review
July 14, 2026 10:39
Contributor
Author
|
@ChenSammi Please review the PR. I have fixed the build failure. The short-circuit PR accidentally told Maven “don’t inherit this antrun plugin to child modules,” and that also stopped child modules from creating target/, which caused the propertyFile.txt failure. |
Contributor
|
Contributor
|
Think the problem is apache/ozone-docker-runner#76 reverted libhadoop download, and also 10513 is not in yet. |
Contributor
Yes. The docker image is updated without the built-in libhaoop.so anymore. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Provide a one-liner summary of the changes in the PR Title field above.
It should be in the form of
HDDS-1234. Short summary of the change.Please describe your PR in detail:
perspective not just for the reviewer.
the Jira's description if the jira is well defined.
issue investigation, github discussion, etc.
Examples of well-written pull requests:
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-10685
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests, workflow run on the fork git repo.)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this.)