Closed rafikc30 closed 2 years ago
@rafikc30, please talk to @aweisser how we're going to handle changes on this fork. AFAIK the master branch here should be mostly up to date with the official master branch. I'm not entirely sure what the best way to handle our diverging code is.
@rluetzner I think this change should also be considered to be part of our "performance PR". And maybe also something that we can bring upstream. Can you please take a look at it!?
@rafikc30 , can you select the 'iternity' branch as the target? This will trigger the GitHub CI and give us some feedback on tests. We do have at least one flaky test currently, so don't be surprised if the CI complains. 😉
AFAIK all of these changes made it into the iternity-rb branch one way or another. Most of the issues were already addressed by MinIO's upstream.
Description
Motivation and Context
How to test this PR?
Types of changes
Checklist:
commit-id
orPR #
here)