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
If the same OpId appears with different operations, it may cause errors when applying the op due to unmet preconditions—for example, the target container ID does not exist, or the insertion position exceeds the list length. Currently, when such cases occur, the import process panics directly, leaving the LoroDoc in an unrecoverable state. A better API design would return an error without affecting the current oplog or doc state. In the current architecture, this requires us to implement an internal “oplog rollback.”