Recording wont exit when using P10k's instant prompt
Pytness opened this issue · comments
Describe the bug
asciinema rec wont terminate when exiting zsh shell if using p10k-instant-prompt.
To Reproduce
Steps to reproduce the behavior:
- ascinema rec -c "zsh"
- ...
- exit
- asciinema keeps recording
Expected behavior
Stop recording
Versions:
- OS: Ubuntu 22.04
- asciinema cli: asciinema 3.0.0-beta.2
Hmm, probably a deadlock.
What happens when you record with -c bash and launch zsh from bash manually?
It hangs after exiting bash.
Here is a recording i made with a great tool i found:
Just tried to reproduce it – I have zsh, p10k and instant prompt enabled on my Linux Mint x86_64 PC and I wasn't able to. It worked just fine.
Out of curiosity, are you sure you have only one installation of asciinema on your machine? Because the version you specified yells at you for saying where you want to store the recording. Can it be that you have both the rust + python version available on your path and Bash and ZSH get it mixed up?
I dont think so. Its a fresh install through cargo install --git ... and whereis outputs the expected .cargo/bin.
By yelling you mean ::: Recording session started, writing to test.cast?
To be clear, I dont see the problem when I comment out the lines sourcing the instant prompt script. Could be something related? I will try using a newer version, maybe it is just outdated.
You can try latest develop, yeah.
Btw, what terminal application do you use?
I am seeing the error on a WSL2 Ubuntu through Wezterm and on an Arch install through ssh in Wezterm
I tried it now on Arch, using Wezterm, with zsh, p10k, instant prompt (selected verbose mode in the setup wizard), but can't reproduce it either.
When you ssh to the Arch install, this is from Wezterm running on Windows maybe?
I installed p10k again (deleting instant prompt script) and Im getting same results.
When you ssh to the Arch install, this is from Wezterm running on Windows maybe?
Yes it is, but Im getting the same problem when connecting through other apps (I tried with an Android app, JuiceSSH)
Maybe this is something in your dotfiles / ZSH setup. Might be worthwhile to go as vanilla as possible and re-add your config things and see where it breaks?
Reason is: I know that when instant prompt launches and there is some kind of delay for it to launch caused by other things in the dotfiles, it will print out things. Maybe this is the case here?
Ok, so given it's the same on JuiceSSH, we can rule out Wezterm.
However I'm confused about instant prompt. You first wrote:
To be clear, I dont see the problem when I comment out the lines sourcing the instant prompt script.
And then:
I installed p10k again (deleting instant prompt script) and Im getting same results.
So it does or does not work without instant prompt?
It does work without instant prompt.
I removed the instant prompt script before reinstalling p10k (and configuring) to ensure the last version is installed. Sorry for the confusion.
I will try and bisect where else could it break.
From the demo you recorded it seems to me that the zsh process actually doesn't fully exit. asciinema finishes when the shell process exits and the allocated PTY for the shell gets closed. So, for some reasone the slave side of the PTY doesn't get closed. (this is probably not useful to you, writing this more as a note for myself :))
Doing kill -9 $$ outputs Killed but still the same issue.
Are you able to install asciinema 2.4.0 and test with it?
Yes, same result. (I uninstalled the rust version)
I am playing with the source code and It gets stuck at pty::handle_child on execvp.
It seems to me that there is not much to be done?
Right, so this confirms that zsh process doesn't exit, for some reason.
Can you try recording with the script command instead of asciinema? Or with ttyrec?
Using script zsh exits.
Comparing with the script command source code, I found out it calls some function ul_pty_signals_setup.
In that function it sets some signals:
sigaddset(&ourset, SIGCHLD);
sigaddset(&ourset, SIGWINCH);
sigaddset(&ourset, SIGALRM);
sigaddset(&ourset, SIGTERM);
sigaddset(&ourset, SIGINT);
sigaddset(&ourset, SIGQUIT);
I noticed that in asciinema, the sigalrm and sigchld are not being handled.
Handling this signals allows zsh to exit nicely.
I will open a PR.