Skip to content
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

fix(bar): prevent komorebi connection from staling #1203

Merged

Conversation

alex-ds13
Copy link
Contributor

Sometimes the bar would randomly stop receiving notifications from komorebi and would stop updating the Komorebi widget. This feels to me that the reason is the same one that used to happen on the process_commands from komorebi where the socket would get stuck reading an empty connection. This commit adds a read timeout to the socket to prevent that from happening and hopefully it should stop those situations where the bar would stop receiving notifications.

There were some users reporting on Discord that the bar would sometime stop updating the workspaces widget and I have faced that as well! Hopefully this should fix that. I looked if there was an opened issue on github related to this but couldn't find any, so maybe it was just reported on Discord.

Sometimes the bar would randomly stop receiving notifications from
komorebi and would stop updating the `Komorebi` widget. This feels to me
that the reason is the same one that used to happen on the
`process_commands` from `komorebi` where the socket would get stuck
reading an empty connection. This commit adds a read timeout to the
socket to prevent that from happening and hopefully it should stop those
situations where the bar would stop receiving notifications.
@LGUG2Z LGUG2Z merged commit 9c78fcc into LGUG2Z:master Dec 26, 2024
6 checks passed
@alex-ds13 alex-ds13 deleted the fix(bar)/komorebi-connection-was-getting-stuck branch December 27, 2024 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants