ANSI Escape Sequences Populating in Geodesic with Atmos 1.158.0

[RoseSecurity]

Describe the Bug

• ANSI escape sequences are populating in Geodesic when upgrading from Atmos 1.157.0 to 1.158.0 for every Atmos command

 √ . [infra] (HOST) workspace ⨠ atmos version

 █████  ████████ ███    ███  ██████  ███████
██   ██    ██    ████  ████ ██    ██ ██
███████    ██    ██ ████ ██ ██    ██ ███████
██   ██    ██    ██  ██  ██ ██    ██      ██
██   ██    ██    ██      ██  ██████  ███████


👽 Atmos 1.158.0 on linux/arm64

^[]11;rgb:1616/1818/1a1a^[\^[[49;1R ⧉  Locally Built Docker Image (infra)
 √ . [infra] (HOST) workspace ⨠ 10;rgb:ffff/ffff/ffff;1R11;rgb:1616/1818/1a1a;1R

Expected Behavior

• The output of command should not contain ANSI sequences

 √ . [infra] (HOST) workspace ⨠ atmos version

 █████  ████████ ███    ███  ██████  ███████
██   ██    ██    ████  ████ ██    ██ ██
███████    ██    ██ ████ ██ ██    ██ ███████
██   ██    ██    ██  ██  ██ ██    ██      ██
██   ██    ██    ██      ██  ██████  ███████


👽 Atmos 1.158.0 on linux/arm64

Steps to Reproduce

• Upgrade from Atmos 1.157.0 to 1.158.0
• Build Geodesic
• Run an Atmos command

Screenshots

No response

Environment

• Geodesic v3.4.0 and v4.0.0

Additional Context

No response

[osterman]

This was first reported in #1026 and caused when logs.file is set to /dev/stdout, I believe. It should never have been /dev/stdout as that will cause problems with any command that produces structured output (e.g. JSON), like in atmos describe * commands

This was fixed in:

• properly handle stdout, stderr, and null #1029

Relates to:

• Weird escape code issues with v1.158.0 #1026

[osterman]

These changes were released in v1.160.2.

[osterman]

Please re-open if you're still having the problem