[MongoDB Storage] Increase timeouts for checksums from 40s -> 80s

[rkistner]

#300 introduced proper error messages for checksum queries timing out. A side effect of that was also reducing the 60s connection-based timeout to a 40s query-specific timeout.

While the results are cached in memory and incrementally updated, in some cases the initial calculation takes too long, causing the service to repeatedly run the same query. We've seen this hit the 40s timeout when calculating checksums over around 5-10 million operations at a time.

This is a quick-fix that just doubles the timeout, which should make it safe to sync up to around 10 million operations per user. A proper future fix will focus on significantly reducing the time needed to calculate these initial checksums, after which we can reduce the timeout values again.

[changeset-bot]

🦋 Changeset detected

Latest commit: 78dd99d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 12 packages

Name	Type
@powersync/service-module-mongodb-storage	Patch
@powersync/lib-service-mongodb	Patch
@powersync/service-core	Patch
@powersync/service-image	Patch
@powersync/service-schema	Patch
@powersync/service-module-mongodb	Patch
@powersync/service-module-mysql	Patch
@powersync/service-module-postgres	Patch
@powersync/service-core-tests	Patch
@powersync/service-module-core	Patch
@powersync/service-module-postgres-storage	Patch
test-client	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR