notification pipeline stalls

[rakslice]

In the installed copy of twitch-notifier-go on my system (I'm not sure exactly what version, but could be current) occasionally the notification queue stalls and notifications are not shown as streams go online. Then, some time later, I interact with the app (clicking taskbar icon) and then whatever notifications have been queued in the intervening time are shown. During the stall time the app appears to be running and polling the API normally and updating online streams shown the window.

Background:

The implementations of popup notifications on some platforms require that only one notification be fired at a time for correct operation. When a stream goes online, a notification goes into a queue, and initially a the first notification is kicked off. Then the handlers for the click and timeout events for the notifications, after doing the appropriate actions for the current notification if any, cause the next notification to be kicked off, and so on until the queue is empty.

[rakslice]

Log showed a normal notification before the stop several hours ago, then several hours of normal polling, then a notification clicked event, then normal messages for the queued notifications

[rakslice]

Add a ~ 20s timeout as a workaround?

[rakslice]

Around Windows 10 Fall Creators Update (1709) or maybe the major update before that, the behaviours of the notifications changed in some important ways:

• the copy of twitch-notifier-go launched on startup that doesn't have its window open can't display notifications
• the last 20 notifications are now kept in the action center, as is done for applications that use newer windows notification specs

The new action center behaviour might make sending all the notifications at once a good alternative on this version of Windows; that may alleviate notification pipeline stalls