"Mehdi has noticed that Pulse doesn’t save properly and has lost his changes"
I tested a few scenarios and the following sequence would cause problems:
User A opens dashboard D
User A saves dashboard D
Server restarts
user A clicks reconnect
user A clicks save (red popup says it failed).
The failure only occurs when the server restarts and does notify the user with a red popup.
This failure was due to optimistic caching to make dashboards load faster.
We hadn't properly considered the multiple writes scenario.
Integration tests couldn't catch it as the cahing is within the browser.
user-ml reported losing saved dashboards.
"Mehdi has noticed that Pulse doesn’t save properly and has lost his changes"
I tested a few scenarios and the following sequence would cause problems:
Integration tests couldn't catch it as the cahing is within the browser.