Chanseok Oh

For #3409, I think I know what exactly is the problem, but ~~I have trouble reproducing this~~. Filed a fix (https://github.com/googleapis/google-http-java-client/pull/1427) against the library. For #3058, yeah, I haven't been...

#3409, which caused an outright no-go friction to many people with the "premature end of chunk" error, has been [fixed upstream](https://github.com/googleapis/google-http-java-client/pull/1427). ~~New versions of the Google HTTP libraries with the...

Sorry, I was dumb. The fix was merged on Sep 23, while 1.40.0 was released on Aug 26. We still have to wait for a new release. Sorry for the...

@famod apart from those listed here (one of which is critical), I'm not aware of anything else. But generally speaking, there's always a chance of behavior changes whenever you upgrade....

@famod Google HTTP Client 1.40.1 is released.

Not sure if we will look into this soon, but I have briefly gone over the [Docker Content Trust (DCT) doc](https://docs.docker.com/engine/security/trust/content_trust/) to see what it is, but I'm still completely...

Based on what you said, I don't really think it's due to the Gradle daemon starting up. Are you caching Gradle and Maven artifacts? You can use [`actions/cache`](https://github.com/actions/cache/blob/main/examples.md#java---gradle).

And this only matters when you enable the Maven parallel builds (`-T `) or run multiple Jib processes simultaneously on the same host. (And only when the base image layers...

@mpeddada1 this issue is a different one. #2780 was only in the context of multi-arch support.

@nhoughto thanks for the feedback. As mentioned in this issue, what you said makes sense, and this is something not ideal. It's only that it would be a pretty complex...