vt921102 commented on PR #8692:
URL: https://github.com/apache/hadoop/pull/8692#issuecomment-5866972803

   Thanks @anujmodi2021, and thanks for merging the trunk change.
   
   This PR already targets `branch-3.5`, so I have refreshed it rather than 
opening a
   new one. It is now a clean cherry-pick of the merged trunk commit 
`e8783aa592`
   onto the current `branch-3.5` head, with the commit message preserved:
   
   ```
   HADOOP-19973. Hadoop file system can not browse the folder that has children
   folder with colon in Windows. (#8536)
   
   Contributed by Le Van Toan
   ```
   
   The cherry-pick applied without conflict and the patch is byte-identical to 
the
   trunk commit — same two files, `AbfsClient.java` (+1/-2) and 
`TestAbfsClient.java`
   (+43). No adaptation was needed: `branch-3.5` is already on JUnit 5 and has 
the
   same `AbfsDfsClient` constructor and 
`AbfsClientContextBuilder.withFileSystemId`,
   so the test is unchanged from trunk.
   
   I am rerunning the full `hadoop-azure` integration suite against 
`branch-3.5` and
   will post the endpoint declaration and results here once it finishes, in the 
same
   form as the trunk run.
   
   Note on the `Build` check: it reports `action_required` because
   `.github/workflows/build_and_test.yml` was added to trunk by HADOOP-19858 on
   2026-04-22, after `branch-3.5` was cut, so no run of that workflow can exist 
for
   this branch. This affects every PR against `branch-3.4`/`branch-3.5`. Apache 
Yetus
   and `jenkins/pr-merge` are the meaningful checks here.
   
   There is also #8693 for `branch-3.4`, since HADOOP-19973 has fix versions 
3.4.4 and
   3.5.1. Happy to refresh that one the same way once `branch-3.5` is in.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to