How to use electricCollection.awaitTxId correctly

[sudoskys]

I use it with createTransaction.
When doing updates in quick succession or in poor network conditions, I will get a lot of Timeout waiting for txId: errors.

Should I increase the timeout of awaitTxId?

db/packages/db-collections/src/electric.ts

Lines 297 to 300 in f13c11e

	const awaitTxId: AwaitTxIdFn = async (
	txId: Txid,
	timeout: number = 30000
	): Promise<boolean> => {

  const transaction = createTransaction({
    autoCommit: false,
    mutationFn: async () => {
      const response = await deleteConversation({ chatId });
      if (!response.txid)
        throw new Error('API did not return a transaction ID');
      await conversationsCollection.utils.awaitTxId(response.txid);  
    },
  });

  transaction.mutate(() => {
    conversationsCollection.delete(chatId);
  });

  await transaction.commit();

I also noticed that using await in a mutationFn to wait for awaitTxId() seems to block the UI.

[KyleAMathews]

Block the UI how?

Note there was a breaking change for awaitTxId #245

That same pr added new debugging logs which you can enable #220 (comment)

[KyleAMathews]

What's the issue?

[sudoskys]

After continuous and rapid operations, it seems that some optimistic states cannot be immediately reflected in the UI.

[KyleAMathews]

Ah ok! I noticed that recently too. I think it's a recent regression and I'm planning on investigating it Monday cc @samwillis

[KyleAMathews]

Hmm I went to reproduce it again today on main... and it was working perfectly... so apparently we fixed it? Accidentally 😅

[sudoskys]

oh, I'll try it

[gruckion]

@sudoskys what's the current state of this discussion, can you provide a update / conclusion with example to help others <3

[sudoskys]

After several updates, this issue has disappeared!

The only issue I had with Sentry was Cannot insert document with key "xxxxx" from sync because it already exists in the collection, but I believe this was caused by manual user intervention.

[sudoskys]

Wait, I don't think I actually tested it.

[marbemac]

Cannot insert document with key "xxxxx" from sync because it already exists in the collection

@sudoskys were you by any chance inserting records into the collection before sync was started? I've been seeing this log every once and a while, related to inserting records before sync started.

[sudoskys]

@marbemac This possibility cannot be ruled out

[sudoskys]

After a period of monitoring, this problem no longer occurs! Just update everything to the latest version.

[sudoskys]

I think this can be closed? Thanks everyone