-
Notifications
You must be signed in to change notification settings - Fork 40.8k
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
Accept progress on numbers >2GB #43328
Accept progress on numbers >2GB #43328
Conversation
@kgb-financial-com Thanks for the PR. Unfortunately, this doesn't qualify as an obvious fix as it changes functionality. Please sign the CLA. |
Thanks. Please give me a few days to get approval from our top brass. |
This fix is needed to push images of a file size >2GB without provoking build failures.
d74d3d5
to
2a8ed5a
Compare
@kgb-financial-com Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
@kgb-financial-com Thank you for signing the Contributor License Agreement! |
I have removed the tag as obvious fix from the original pull request description, and signed the CLA. Please proceed. :) |
Thanks for signing the CLA. Technically speaking, this is a breaking change as the constructor of |
Update `ProgressUpdateEvent` to support images of a file size >2GB without provoking build failures. See gh-43328
Restore `int` returns for existing methods and deprecate them in favor of a new `asPercentage()` method. See gh-43328
Looking at our own code, we only have one place that we call those methods which we can replace with a new I agree with @wilkinsona that this class is mostly internal so I think we can be aggressive about removing the deprecated methods in 3.5. Thanks for the contribution @kgb-financial-com |
Docker ProgressUpdateEvent may report file sizes larger than 2GB, but int has been used as the target type on parsing the according json output. If we attempt to push an image with a total size of >2GB, this will result in a build failure (although the image will still be pushed correctly).
This Pull Request fixes that by changing the affected types from int to long.