🐞 `dagger.exe` has no output. v0.11.0. Windows. about dagger

[levlaz]

@jpadams and I did a bit of pairing and were able to figure some things out.

It looks like the issue is with the new TUI + windows, specifically when --progress-auto by default you get no output in windows. However, if you switch to --progress=plain then we are able to see all the right output.

init still does not work regardless of the output settings due to the issues covered here: #7003

$ ./dagger.exe --progress plain version
dagger v0.11.0 (registry.dagger.io/engine) windows/amd64

[fcbry]

thank you @jedevc

[fcbry]

Checked out and attempted to build from main

commit d3a11cf89ec9685d4c60737d3ab2af7bd4e558e0 (HEAD -> main, origin/main, origin/HEAD)
Author: Helder Correia <[email protected]>
Date:   Thu Apr 11 11:17:59 2024 +0000

❯ cd .\cmd\dagger ; go install ; go build . ; dagger.exe --help

dagger\cmd\dagger on  main via 🐹 v1.22.2 took 3s

(no output)

[pjmagee]

I thought it was me. I tried everything, nothing seems to work. I checked my paths, tried to run it from Powershell, Cmd etc. This is a big issue for the tutorial

[pjmagee]

A "workaround" for now could be to use WSL? I managed to get it working fine on Ubuntu WSL. WSL saves the day 🗡️

[fcbry]

A "workaround" for now could be to use WSL? I managed to get it working fine on Ubuntu WSL. WSL saves the day 🗡️

Yes WSL is an option, but hopefully it gets resolved, only working on *nix, makes it a bit of a harder sell. I'd be willing to help in my free time with setting github windows builds (1/4 century nix, but working in a windows shop now).