-
Notifications
You must be signed in to change notification settings - Fork 6.4k
fix: use getObjectNInfo to avoid bytes.Buffer usage #11428
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
Conversation
few places were still using legacy call GetObject() which was mainly designed for client response writer, use GetObjectNInfo() for internal calls instead.
Mint Automation
11428-23b4c4f/mint-gateway-azure.sh.log:11428-23b4c4f/mint-large-bucket.sh.log:11428-23b4c4f/mint-compress-encrypt-dist-erasure.sh.xtrace:Deleting image on docker hub |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
fix: use getObjectNInfo to avoid bytes.Buffer usage
Motivation and Context
few places were still using legacy call GetObject()
which was mainly designed for client response writer,
use GetObjectNInfo() for internal calls instead.
How to test this PR?
Nothing should change in terms of functionality
reduces the occasional memory usage
Types of changes
Checklist:
commit-idorPR #here)