dx bundle Silently Fails in CI by Swallowing Cargo stderr. help!

[dan-da]

Hi, I'm using dx bundle (v0.6.3) in GitHub Actions, and it's swallowing cargo build errors.

When dx bundle is run in a non-interactive CI environment (where it's not connected to a TTY and output is piped), the TUI logic appears to be swallowing the stderr from the cargo subprocess.

This means that when cargo fails (due to a linker error, etc.), dx doesn't print the cargo error. It just exits with a generic message like err=Other(Build did not return an executable).

This is different from running locally in an interactive terminal, where cargo errors are shown correctly. This behavior makes debugging CI build failures extremely difficult.

Expected Behavior: In a non-interactive CI environment, dx bundle should print the raw stderr from cargo when a build fails.

Actual Behavior: dx bundle's TUI swallows the stderr and reports a generic, useless error.

Example from a CI log:

 203.272s  INFO dx::build::builder: Compiling [550/958]: opentelemetry
524
 206.111s  INFO dx::build::builder: Compiling [551/958]: reqwest
525
 304.811s DEBUG dx::build::builder: Setting builder to failed state
526
 304.816s ERROR dx::build::builder: err=Other(Cargo build failed, signaled by the compiler. Toggle tracing mode (press `t`) for more information.) 
527
 304.835s ERROR dx: err=Other(Cargo build failed, signaled by the compiler. Toggle tracing mode (press `t`) for more information.) 
528
Error: Process completed with exit code 1.

I have tried flags --verbose --trace --json-output. individually and in combination. no improvement. I also tried passing flags to cargo directly without any luck.

[dan-da]

nevermind, I am able to login to CI machine via ssh and use it interactively.