Ned Andreev

Another thing we should improve is the handling of special/non-printable characters in the generated scripts. For example, instead of having an invisible null-byte in the middle of a random string,...

Regarding request bodies, we can check the `content-type` in the HAR file and write any binary bodies as a base64-encoded string in the generated script. And as mentioned in the...

As seen in [this issue](https://github.com/loadimpact/k6/issues/808), another reason for massively refactoring (i.e. rewriting) the HAR converter is the somewhat poor request dependency detection in the current implementation

We shouldn't add the `Content-Length` header to the parameters of requests in the converted scripts. There are a couple of reasons for this: - Before https://github.com/loadimpact/k6/pull/989, k6 would set the...

https://github.com/loadimpact/k6/issues/957 shows that the k6 output in PowerShell has some artifacts, like `µs` instead of `µs` and some glitches in the logo.

Seems like Jenkins might have some of the same issues: https://github.com/loadimpact/k6/issues/1294 I'll rename this issue to be a more generic catch-all for all such visual glitches and UI problems in...

@victorinho, which of the multiple minor issues described here do you experience? Can you give a screenshot and some more details about your environment, like for example the terminal you...

We'll _try_ to fix this in the next k6 version, but I'm not giving any promises... @victorinho, what terminal are you using to run k6? It seems like it doesn't...

A more modern terminal like https://github.com/microsoft/terminal or https://cmder.net/ should work better.

Hmm I'm not sure if I'd consider this a quite a bug, it's more like something between a bug and missing functionality... In any case, it's a very valid point...