#Dagger changes cursor after failing with Docker
1 messages · Page 1 of 1 (latest)
I honestly can't remember, that was on an old dev branch, the codebase has changed a lot since then. Probably better to assume it's unrelated.
dagger run is a thin wrapper around your own tool. By default it takes over printing progress information to your terminal, so it's conceivable that there is a bug in the terminal cleanup. If you file a github issue, it would be very appreciated, that way we can track and try to reproduce.
Make sure to ping @exotic marsh on that issue, he wrote most of that terminal UI feature
Yep opening an issue and confirming your Dagger version would be best 🙏 - it should be putting your terminal back into the same state that it was in before, but it depends on what you mean by 'cursor settings' I suppose (visbility? color? etc)
What is the issue? I ran my CI script dagger run npx tsx ci.mts and it made my block cursor disappear. Dagger version dagger v0.11.0 (registry.dagger.io/engine) darwin/arm64 Steps to reproduce dagg...
Curiously, rerunning just "dagger" fixes it.