Ned Andreev

And it's not even using the `DefaultTransport`, it's creating [its own internal one](https://github.com/golang/go/blob/5ec14065dcc4c066ca7e434be7239c942f0c2e5b/src/net/http/httputil/dump.go#L107-L111) :man_facepalming: Anyway, I'm not sure what the best way for this to be fixed on the k6...

Thanks for opening this issue and sorry for the slow reply! It's a known problem that was previously mentioned in https://github.com/grafana/k6/issues/761 (and probably in other [`new-http` issues](https://github.com/grafana/k6/issues?page=1&q=is%3Aopen+is%3Aissue+label%3Anew-http)) that we'd like...

IIRC we have observed this problem with some weird CI environment that allowed for non-POSIX env vars... Vanilla Windows, Linux and *nix are thankfully saner. I can imagine they have...

Could be :thinking: But it's still a better alternative than incorporating these broken variables in the .tar archive and then being unable to run them in the cloud when someone...

I'll close this now, since, from what I understand, this would be better resolved with a PR to https://github.com/grafana/k6-docs?

My mistake, you are completely right, sorry! :man_facepalming:

I haven't used logr, but we may want to eventually get rid of logrus on the k6 side... It in maintenance-mode (see https://github.com/sirupsen/logrus/blob/master/README.md) and there are plenty of other quite...

This issue was originally opened in the k6 repo, but it's about k6-operator, so I moved it to the https://github.com/grafana/k6-operator/ repo

Thanks for making this issue! We'd like to have gRPC streaming, but at least the server streaming and bi-directional streaming parts are somewhat blocked by our lack of event loops...

Yes! I can't give any promises for when exactly, depends on how we prioritize against a whole bunch of other things, but it's definitely on our short-term roadmap now that...