-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
BUG | failed to send tick event: SendError { .. } #12
Comments
Thanks for reporting! I also experienced this issue a couple of times but I'm not sure why it is happening. I'm guessing maybe it is related to the timing of the tick event and quitting the TUI at the same time. I will investigate. For some context, I initialized this project from the ratatui sync template, I wonder if that repo has the same issue as well. |
An error during send means the other side of the channel stopped listening. It's not an error that should be panicked on, it's the expected way to end the listening (unless you add cancellation in another way). I haven't looked at the source for this, but either ignoring it this error, or exiting any loop, thread or task that it's called from is the right thing to do instead of panicking. |
Just realized we panic on this in the template too: |
I removed the tick event (since it wasn't used anyways) so it should be good now. |
There's a bug for this in ratatui/templates#49 :) |
Describe the bug
I just want to try flawz without any arguments/flags to see how it results. It worked, but when I want to quit I expecting it to end without any logs but it gave me a
panic
warning.To reproduce
Steps to reproduce the behavior:
sudo pacman -S flawz
// Successfulflawz
q
to quit.Expected behavior
Exiting with code 0 without any logs
Screenshots / Logs
Software information
Additional context
I also tried to follow the guide on the logs,
First:
It gives null stack backtrace, I followed up with
RUST_BACKTRACE=full
Second:
The text was updated successfully, but these errors were encountered: