-
Notifications
You must be signed in to change notification settings - Fork 718
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
tea.unknownCSISequenceMsg: unknown message type
panics
#1016
Comments
Thanks for reporting this, Tom. Agreed: Bubble Tea should not be panicking here. We'll look into it, and while it may be a bug in Bubble Tea, I do wonder if the panic is happening higher up in chezmoi. By default, Bubble Tea catches panics in Also note that there’s a newer version of Bubble Tea out (v0.26.2; it looks like chezmoi is on v0.25.0 per the stack trace). |
Hey @twpayne; just following up on this. I do believe what we're seeing here is a panic in Chezmoi, with Bubble Tea simply recovering from the panic and restoring the terminal state. That's this item in the stack trace in Chezmoi #3758:
Given that I'm going to close this issue, however in chance I'm wrong and you're able to reproduce the issue please do reopen this and we'll examine it further. |
Ah, I'm sorry, you're totally right. Apologies for the noise. I mistook the However, I see from charmbracelet/bubbles that unexpected messages should be ignored: Thanks again! |
Describe the bug
bubbletea panics with the message
tea.unknownCSISequenceMsg: unknown message type
occasionally. I'm unable to reproduce this, but "Effective Go" states that libraries should not panic.Setup
This was reported by users in:
chezmoi diff
panics withtea.unknownCSISequenceMsg: unknown message type
twpayne/chezmoi#3662chezmoid apply
(anddump
) cause a Go panic twpayne/chezmoi#3758To Reproduce
I am unable to reproduce it.
Source Code
See above.
Expected behavior
bubbletea should not panic, and it it does, it should include sufficient information to know what went wrong (e.g. the CIS sequence that caused the panic).
Screenshots
n/a
Additional context
Happy to help debug this!
The text was updated successfully, but these errors were encountered: