No response from CLI for init and call commands

[sharp shell]

Hi, I installed v0.9.11 version of dagger. Running dagger version and dagger --help prints outputs to the console. But the CLI is stuck and doesn't print anything if I try to run dagger init --name=my-module --sdk=go or dagger -m github.com/shykes/daggerverse/hello call hello.

OS/Arch is linux/amd64. Please help me to debug this 🙏

Those commands used to work when I was trying out v0.9.7 or v0.9.10 IIRC.

[echo arrow]

👋 if you do a docker ps do you have a Dagger engine running?

[sharp shell]

Nope. Seems like the dagger engine is not running.

[raven dagger]

I had a bit of weirdness earlier with this too, I think the first time you get a new version it takes a little while to download the engine in the background. if you run it in debug mode do you see anything? I think (i have kind of a slower connection at home) the initial cold start when I downloaded the new version was like 30+ seconds

[echo arrow]

As Conor said, try adding the --debug flag to see if you get the logs about downloading the new engine image

[sharp shell]

Thanks folks! I retried with --debug and I can see output from dagger now. The dagger engine also came up.

Should we aim to log some information when dagger is trying to bring up the dagger engine? That would help avoid confusions for people on slower networks.

[raven dagger]

I think a download indicator in non debug logs would be helpful as well. Or at least SOME sort of visual feedback. The only reason I knew to try it with --debug was because I knew there was a cold start time and that dagger downloads its own engine at first run from previous experience with dagger. I could definitely see this confusing the heck out of someone who is coming in for the first time, and even giving up because they think nothing is happening

[echo arrow]

I recall we had a message for this. cc @grim knot I think the TUI updates for modules are not printing these messages anymore (https://github.com/marcosnils/dagger/blob/2f975ef29ad78e08c5b9328f6db3797b4c57da69/engine/client/drivers/docker.go#L143) while pulling a new engine.

I'm just checking that now

[echo arrow]

yep, can't see that message even if I add the --debug flag to the dagger call using the TUI

[echo arrow]

and it shows using the legacy TUI

[grim knot]

looking into this!

[grim knot]

for the heads up, pushed a fix: https://github.com/dagger/dagger/pull/6704#issuecomment-1964812334

[raven dagger]

I just downloaded 0.10 and confirming that your change fixed it alex, I see the TUI render the engine pull again now