New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐞 Failed run erases the cursor in a terminal #7160
Comments
So I have seen this on zsh on Ubuntu. Also it does something where stdin for future commands doesn't work. For instance if I have a failed dagger run and then I attempt to run a sudo command in the same terminal I can't type in my password. Or if a command requests confirmation that doesn't work. I haven't found a way to fix it other then close the terminal and start fresh. The dagger command does replace the cursor, but stdin is still broken. |
it's easy to reproduce by just not starting Docker on macOS. The same happens in a bash terminal. Using iTerm or Terminal. One way to get the cursor back is to open vi and exit. |
I have seen this in bash on ubuntu. It seems to only happen when running a task fails due to a bug in the pipeline code. |
I also saw this yesterday in bash on ubuntu via a windows client - seems its not specific to OS or shell to me. I updated the title of this issue to make that part a bit more clear. |
More info, the PowerShell is not broken. With reproducing code (Elixir): Mix.install([:dagger])
dag = Dagger.connect!()
{:ok, _} = dag
|> Dagger.Client.container()
|> Dagger.Container.from("alpine")
|> Dagger.Container.with_exec(~w"exit 1")
|> Dagger.Container.stdout()
Dagger.close(dag) |
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
dagger run npx tsx ci.mts
with some Docker stuff that fails.Log output
The text was updated successfully, but these errors were encountered: