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
With the refactoring of the initialization of the document from the document content only happening once we now have a situation where the second attempt of the initialization assumes a y.js state and steps containing the document content, but those steps have never been pushed by the first session as it is read only.
Catched by cypress when the first test is failing and the retry is running into that
Screenshots from the failing tests on main (cannot reproduce locally)
If we are creating a read only session we could always reset the state if no steps and an empty state is present
Just use the document content to show the read only document until a edit session has actually pushed a state (likely preferrable as the cleanup could be too heavy on high traffic documents)
The text was updated successfully, but these errors were encountered:
Steps to reproduce:
With the refactoring of the initialization of the document from the document content only happening once we now have a situation where the second attempt of the initialization assumes a y.js state and steps containing the document content, but those steps have never been pushed by the first session as it is read only.
Catched by cypress when the first test is failing and the retry is running into that
Screenshots from the failing tests on main (cannot reproduce locally)
Briefly discussed options with @mejo-
The text was updated successfully, but these errors were encountered: