Visual glitches on Windows terminals

[w1kman]

When running k6 (that exact command) in Command Prompt (CMD.exe), coloring breaks. There are no problems when running an actuall test (eg k6 run ...)

Checkmark displayed for passed tests, is also "broken"

Running Command Prompt via Windows Terminal seems to negate both problems.

Environment

• k6 version: k6 v0.29.0 (2020-11-11T13:27:19+0000/d9bced3, go1.15.3, windows/amd64)
• OS and version: Microsoft Windows 10 Pro (10.0.19042 Build 19042)
• Docker version and image, if applicable: N/A

Expected Behavior

Colored k6 logo (as when running Command Prompt via Windows Terminal)

Checkmark in test result:

Actual Behavior

Characters intended to color output are visible(ish)

Boxed ? instead of checkmark in test result:

Steps to Reproduce the Problem

1. WIN+R
2. Type cmd, click "Ok" (or press Enter)
3. Type k6, Enter

[jmk0317]

k6 javascript API check(val, sets, [tags]) - CLI - Windows 10 - from both the command prompt and PowerShell - returns this for the check mark

[na--]

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.

[na--]

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 k6, so we don't have a bunch of related issues on the topic. And I guess the only "fix" for these would be to give users a way to disable them and use a simplified ASCII interface, e.g. via the proposed --ui-mode composite option (https://github.com/loadimpact/k6/issues/1376).

[victorinho]

I have the same problem that has been reported, I do not understand how I can solve it ... my version of k6 is: k6 v0.31.1

Can you help me how to solve it?

[na--]

@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 use and the OS type and version?

[victorinho]

@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 use and the OS type and version?

Hello @na-- !

My problem is that some characters appear wrong as seen in the image. Attached image

My operating system is a windows 10 and the version of k6 is: v0.31.1

Thanks!

[na--]

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 support utf-8

[victorinho]

@na-- I am using windows command console (cmd)

Where can I run it from instead?

Regards

[na--]

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

[immavalls]

@na-- The user in https://community.k6.io/t/exporting-rate-to-json-looks-faulty/5707/14 mentions they can't use a more modern terminal and shares more details of what they see with powershell / command prompt and AzureDevOps.

[RafaMalicia]

Hi, does anyone know how to solve this? I'm getting these odd characters, I'm running k6 on Azure DevOps Release Job

Run Info:

2023-10-03T20:01:35.0002052Z Task : Command line 2023-10-03T20:01:35.0002115Z Description : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows 2023-10-03T20:01:35.0002256Z Version : 2.212.0 2023-10-03T20:01:35.0002318Z Author : Microsoft Corporation 2023-10-03T20:01:35.0002393Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line