Piotr Tabor (ptab)

I updated the version of oauth2 in https://github.com/bazelbuild/bazel-gazelle/pull/1582

@Hargne Could you, please, take a look and create PR from the diff (I cannot push a branch here).

Looking at: https://github.com/chainguard-dev/rules_apko/blame/main/apko/private/apko_run.bzl#L29 I assume it's fixed. Shebangs `#!#!` should be fixed as well (but it should cause the functional problems afaiu).

@thesayyn Please take a look in context of your comment: https://github.com/chainguard-dev/rules_apko/issues/42#issuecomment-1850630445 > to avoid hard fails, in case the signature change, we only cache control and data and let signature...

There is long standing issue in bazel: https://github.com/bazelbuild/bazel/issues/13230 for using or internal 'zipper' impl.

Note: I shared some thoughts about the issue in: https://github.com/chainguard-dev/rules_apko/pull/117 > I think that apko used to generate single-arch containers when single arch was given, and now it produces multi-arch...

@mattmoor @jonjohnsonjr @imjasonh : Please take a look at the PR with proposed fix: https://github.com/chainguard-dev/apko/pull/1610

I think that most critical aspect of this issue is addressed: i.e. we don't get stuck for ~2-5min when running in offline mode... Still there are some aspects pending to...

We also stumped on this problem. Either we need to `linkmode=pie` our go_binaries to make the cross-compilation from mac to linux work or apply this patch.

@fmeum @tyler-french - could you please take a look at this patch. Without this (or `linkmode=pie`), the linker on mac os is producing corrupted binaries. Confirmed with 0.48.1 on golang...