Matt Moore

To clarify, the behavior is to hang **_if the activator is in the request path_**. I just ran a setup with `target-burst-capacity: 0` configured globally, and was startled that timing...

cc @jonjohnsonjr I think the hardest part of this now would be determining what to do for `--platform=all` 🤣

I think we should sort out what we want to do for multi-arch first? Is there a way to enumerate all of the platform combination the Go toolchain supports? 😅

Challenge accepted? 😅

@xmlking I suspect the `kodata` problem is related to the permissions of the directory. I see similar problems, but it seems strangely non-deterministic for me. I have a fix for...

See also: https://docs.google.com/presentation/d/1bgoRwNCHqFxFF_JUFtQvtBYVXBmO4u9voWxeFkXISLo/edit

> With the original ko yaml, we have ko:// prefixes What if it only applied to strings with the `$KO_DOCKER_REPO` prefix 😉 EDIT: keeps reading and sees @imjasonh suggesting exactly...

I think we want the directory to exist, even if it is empty.

I don't have a problem with that, though you should confirm it WAI since I think the layers are in the wrong order.

@jonjohnsonjr had a chance to read through. Great writeup, and I agree with your categorization. Looking forward to seeing it in action :)