Bug Reports
Closed

Connectivity still not stable

This report is reopening bug from few days ago:
"Connectivity not stable in 1.11.0"

In the newer version, this bug is fixed, but only in single-member workspaces. When a workspace has more members, the connectivity issue persists.

4 Comments

Posting anonymously

MateuszR·13 days ago(edited)

Good news, it all working fine right now. You can close the ticekt :)

Posting anonymously

Budgero Admin·14 days ago

This should be sorted out in the latest release.
I'll leave this thread open now, so please let me know how it goes, if anything else comes up please share the logs they are super helpfull in debugging this.

Posting anonymously

MateuszR·14 days ago

index-DEQmsSvM.js:12 [Runtime][SyncTransport] Failed to apply catch-up mutation {mutationId: 'mut_82749228-16cb-4077-a733-2a5a00e05a17', error: 'Report not found after update'}

Ns @ index-DEQmsSvM.js:12

(anonymous) @ index-DEQmsSvM.js:12

handleCatchUp @ index-DEQmsSvM.js:12

await in handleCatchUp

processMessage @ index-DEQmsSvM.js:12

handleRawMessage @ index-DEQmsSvM.js:12

a.onmessage @ index-DEQmsSvM.js:12

index-DEQmsSvM.js:12 [Runtime][SyncTransport] catch_up_fallback_snapshot {reason: 'apply_failed', sinceVersion: 1820, localVersion: 1820, spaceId: 'af2c8618-8e55-4ac9-8919-c47746845580'}

Ns @ index-DEQmsSvM.js:12

(anonymous) @ index-DEQmsSvM.js:12

handleCatchUpUnsafe @ index-DEQmsSvM.js:12

handleCatchUp @ index-DEQmsSvM.js:12

await in handleCatchUp

processMessage @ index-DEQmsSvM.js:12

handleRawMessage @ index-DEQmsSvM.js:12

a.onmessage @ index-DEQmsSvM.js:12

index-DEQmsSvM.js:12 [Runtime][SyncTransport] Failed to apply catch-up mutation {mutationId: 'mut_82749228-16cb-4077-a733-2a5a00e05a17', error: 'Report not found after update'}

Ns @ index-DEQmsSvM.js:12

(anonymous) @ index-DEQmsSvM.js:12

handleCatchUp @ index-DEQmsSvM.js:12

await in handleCatchUp

processMessage @ index-DEQmsSvM.js:12

handleRawMessage @ index-DEQmsSvM.js:12

a.onmessage @ index-DEQmsSvM.js:12

index-DEQmsSvM.js:12 [Runtime][SyncTransport] catch_up_fallback_snapshot {reason: 'apply_failed', sinceVersion: 1820, localVersion: 1820, spaceId: 'af2c8618-8e55-4ac9-8919-c47746845580'}

Ns @ index-DEQmsSvM.js:12

(anonymous) @ index-DEQmsSvM.js:12

handleCatchUpUnsafe @ index-DEQmsSvM.js:12

handleCatchUp @ index-DEQmsSvM.js:12

await in handleCatchUp

processMessage @ index-DEQmsSvM.js:12

handleRawMessage @ index-DEQmsSvM.js:12

a.onmessage @ index-DEQmsSvM.js:12



Clients are not connected while bug is active.

Posting anonymously

Budgero Admin·14 days ago

Do you mind pasting the error log again please? Also are other clients connected at the same time when you experience this bug?

Posting anonymously