You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Almost certainly a race condition. Hitting Delete to remove a notification removes that notification and then shows the Rofi window again. But sometimes the notification I just deleted still appears in the list when the Rofi window reappears. In this situation, if I Esc out of Rofi and pop Rofication up again, the notification I deleted is no longer showing. This to me indicates a race condition.
A possible solution might be to save the ID of the most recently deleted notification, and always exclude that ID when showing the current list. This approach is optimistic that the notification system received and processed the delete request, but pessimistic that the operation completed by the time the Rofi UI was redisplayed.
The text was updated successfully, but these errors were encountered:
I think a fix is trivial to do, rofication-gui.py should not create a second connection to send the delete, but use the existing connection.. making sure it is serialized.
edit: looking at the code after many years, this thing needs to be rewritten 😝
Almost certainly a race condition. Hitting
Delete
to remove a notification removes that notification and then shows the Rofi window again. But sometimes the notification I just deleted still appears in the list when the Rofi window reappears. In this situation, if IEsc
out of Rofi and pop Rofication up again, the notification I deleted is no longer showing. This to me indicates a race condition.A possible solution might be to save the ID of the most recently deleted notification, and always exclude that ID when showing the current list. This approach is optimistic that the notification system received and processed the delete request, but pessimistic that the operation completed by the time the Rofi UI was redisplayed.
The text was updated successfully, but these errors were encountered: