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
In the event of a persistence conflict an error is shown in the JavaScript console, but is not displayed in the UI to the user.
Expected vs Current Behavior
The user should be informed of any persistence errors as this may impact their workflows.
Steps to Reproduce
The only way that I've found of consistently triggering a persistence conflict is by repeatedly renaming an object. They also happen sporadically in other cases. Note that this has highlighted another regression.
Rename an object
Renamed it again
Open the JavaScript console and observe that a persistence conflict has occurred, but none has been displayed to the user.
I saw a few forms of this during testathon on 07/12/22. I would edit the properties on a hyperlink or a web page object in a subfolder, and the display would reflect the properties for a few seconds, but would then revert to the old settings. @ozyx noticed multiple PUT calls being made, including a PUT call with the old properties.
@khalidadil see also #5398 , I believe this is the same issue. And unless anyone has experienced this with localStorage, I also believe this bug is specific to CouchDB persistence?
Summary
In the event of a persistence conflict an error is shown in the JavaScript console, but is not displayed in the UI to the user.
Expected vs Current Behavior
The user should be informed of any persistence errors as this may impact their workflows.
Steps to Reproduce
The only way that I've found of consistently triggering a persistence conflict is by repeatedly renaming an object. They also happen sporadically in other cases. Note that this has highlighted another regression.
Environment
Impact Check List
Additional Information
The text was updated successfully, but these errors were encountered: