This is an automated email from the ASF dual-hosted git repository.

adoroszlai pushed a change to branch ozone-2.1
in repository https://gitbox.apache.org/repos/asf/ozone.git


    from de24a1ad0c4 HDDS-13978. OMLockDetails should not be used as the object 
returns a ThreadLocal Object (#9346)
     new eedd9c3c37c HDDS-14366. Bump log4j2 to 2.25.3 (#9597)
     new 5e186e1b64c HDDS-14633. ozonescripts/test.sh fails with image already 
exists (#9762)
     new ca390c6d80a HDDS-14635. kubernetes check fails after restarting 
datanodes (#9772)
     new 69fc278996f HDDS-13069. Error stopping S3 Gateway admin webserver 
(#9776)
     new 3c03e0fb06c HDDS-13977. Bump Netty to 4.1.128, gRPC to 1.77.0 (#9349)
     new 38cb06e01fc HDDS-14522. Bump Netty to 4.1.130, gRPC to 1.77.1 (#9691)
     new b7995a2867a HDDS-14171. Use workflow inputs in run command via 
environment variable (#9498)

The 7 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .github/workflows/check.yml                        | 22 +++++++++++++++-------
 .github/workflows/intermittent-test-check.yml      | 12 +++++++-----
 .github/workflows/repeat-acceptance.yml            |  3 ++-
 .../hadoop/hdds/server/http/BaseHttpServer.java    |  7 ++++++-
 .../main/compose/ozone-om-ha/docker-compose.yaml   |  5 -----
 .../main/compose/ozonescripts/docker-compose.yaml  |  3 ---
 .../src/main/k8s/definitions/ozone/config.yaml     | 11 +++++++----
 .../dist/src/main/k8s/examples/ozone/test.sh       |  1 +
 hadoop-ozone/dist/src/main/k8s/examples/testlib.sh | 17 +++++++++++++++++
 .../java/org/apache/hadoop/ozone/s3/Gateway.java   |  4 ++--
 pom.xml                                            |  8 +++-----
 11 files changed, 60 insertions(+), 33 deletions(-)


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

Reply via email to