David Hoover

I've seen just that with our setup; the repo doesn't cope with auth in the url, it really has to go into headers. I've been using a hack described in...

There are also issues that bazel will blindly invoke a bazillion maven_jars in parallel and bring a machine to its knees: https://github.com/bazelbuild/bazel/issues/5452

I'm hitting this, too, and put together an example over here: https://github.com/deadmoose/no-url The [`jar_artifact`](https://github.com/deadmoose/no-url/blob/master/3rdparty/workspace.bzl#L60-L61) expects to have `hash["url"]` and `hash["sha256"]`, but if you look at the actual definitions in [`list_dependencies`](https://github.com/deadmoose/no-url/blob/master/3rdparty/workspace.bzl#L69-L70)...

In particular, it appears that using the default resolverType does that, whereas explicitly switching to `resolverType: "coursier"` generates a valid file.

> since even against a no-op call site, you are still creating the Object[] for the invocation? Or am I missing something fundamental here? It's addressed in more detail in...

I've got something cobbled together on my end using a `io.grpc.Context` and a custom logging backend to do similar. IIRC we'd had mixed luck with MDC because it's very thread-oriented,...