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
fix: synchronize mirror writes within transactional sync path
safeMirrorDbHandler resolves immediately via finally { resolve() }
before the callback executes, making every mirror write fire-and-forget.
When createAndProcessTransaction calls mirrorTransaction.commit(), the
detached writes may not have completed, producing "commit has been
called on this transaction" errors and leaving the mirror with stale
data.
Add mirrorWrite/mirrorWriteV2 helpers that run the callback directly
(awaited) when a mirrorTransaction is provided, bypassing the
authenticate/reconnect overhead since the caller already started the
transaction. Non-transactional API writes keep the existing
fire-and-forget path via safeMirrorDbHandler.
0 commit comments