Also, StatusAggregator.restart_progress_bubble should be called after any send_notification. In fact, I believe we should make an aggregating/updating mechanism (like the one in FileDiscoveryBubble) in an upcoming branch, so if more events are received they are shown on the current notification.
For instance, turning on the computer and finding out 3 new udfs are available. With this branch we'll see three bubbles one after the other, each popping up immediately after the previous is hidden. With an updating mechanism we would only see one bubble, and the message would be updated as soon as the second and third udfs are found.
Also, StatusAggregato r.restart_ progress_ bubble should be called after any send_notification. In fact, I believe we should make an aggregating/ updating mechanism (like the one in FileDiscoveryBu bble) in an upcoming branch, so if more events are received they are shown on the current notification.
For instance, turning on the computer and finding out 3 new udfs are available. With this branch we'll see three bubbles one after the other, each popping up immediately after the previous is hidden. With an updating mechanism we would only see one bubble, and the message would be updated as soon as the second and third udfs are found.