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
Have 10+ notifications, ideally spaced with a few minutes to make them easier to recognize (or different contents)
Have a slow instance
Open the bell icon dropdown
Quickly click on the delete icon of the top notification, then for the next one as it appears on top, etc
Expected result
All notifications gone
Actual
Notifications pop up again.
The network console did show a 200 OK for the DELETE operations.
If I refresh the page, the notifications are gone.
Versions
Observed on NC 22 on c.nc.com with notifications that came from people answering to a poll from the forms app.
Analysis
I suspect that the frontend code is not properly handling multiple deletions in parallel, and the refresh code might mistakenly reuse an old version of the collection.
The text was updated successfully, but these errors were encountered:
You delete another notification (and it's immediately hidden in the UI)
The server finishes sending the notification with the notification you deleted in 5.
The UI adds the notification again as it is in the list of your notifications
But seeing those steps, it could also happen when you happen to delete exactly when the 30s sync of notification happens without the notify_push (it's just very much more unlikely).
What we could do is keep a record of successful deletes and filter them out manually on the results, but it sounds rather messy.
Steps to reproduce
Expected result
All notifications gone
Actual
Notifications pop up again.
The network console did show a 200 OK for the DELETE operations.
If I refresh the page, the notifications are gone.
Versions
Observed on NC 22 on c.nc.com with notifications that came from people answering to a poll from the forms app.
Analysis
I suspect that the frontend code is not properly handling multiple deletions in parallel, and the refresh code might mistakenly reuse an old version of the collection.
The text was updated successfully, but these errors were encountered: