Inirit

Okay I think I figured out the problem. I was using the localstack/localstack image and not localstack/localstack-pro. That's my bad, but a warning from the core image would have saved...

EDIT: This did not repro for me when I downgraded to v16.18.1, so my repro may not be the same as the original issue despite the surface level error message...

>I have never used `dotnet publish` for an class library so I'm curious what you usecase is? It's actually in service of what I touched on in #359. dotnet, or...

Got it, I appreciate the honesty. I'll discuss possible directions with my team. While that's happening, there's at least two required changes that I'd like to point out for the...

I have a very naive suggestion for a workaround (at least for my purposes): Expose all the files of a NuGet package as a filegroup. This filegroup would exist alongside...

One more thing: Since Artifactory is used, it could be suggested to use a v3 URL instead to work around this problem. However, when using paket2bazel to generate the bzl...

I'd be concerned with there being a specific code path for Artifactory, therefore opening up an unbounded surface area of custom handling for various NuGet providers. Rather, it's my assumption...

So I think I have a viable workaround for this issue. The [experimental_downloader_config](https://bazel.build/reference/command-line-reference#flag--experimental_downloader_config) command line option allows you to intercept and rewrite URLs used by the Bazel downloader. With this...