Paul Fitzpatrick e30d0fd5d0 (core) fix sync to s3 when doc is marked as dirty but proves to be clean ... Summary: This fixes a two problems: * A mistake in `KeyedMutex.runExclusive`. * Logic about saving a document to s3 when the document is found to match what is already there. `HostedStorageManager.flushDoc` could get caught in a loop if a document was uploaded to s3 and then, without any change to it, marked as dirty. Low level code would detect there was no change and skip the upload; but then the snapshotId could be unknown, causing an error and retries. This diff fixes that problem by discovering the snapshotId on downloads and tracking it. It also corrects a mutex problem that may have been creating the scenario. A small delay is added to `flushDoc` to mitigate the effect of similar problems in future. Exponential backoff would be good, but `flushDoc` is called in some situations where long delays would negatively impact worker shutdown or user work. Test Plan: added tests Reviewers: dsagal Reviewed By: dsagal Differential Revision: https://phab.getgrist.com/D2654		2020-11-10 08:12:31 -05:00
..
client	(core) Close previous example card in the rare cases when a second one might be triggered	2020-11-09 23:46:47 -05:00
common	(core) fix sync to s3 when doc is marked as dirty but proves to be clean	2020-11-10 08:12:31 -05:00
gen-server	(core) support GRIST_WORKER_GROUP to place worker into an exclusive group	2020-11-02 15:46:46 -05:00
plugin	(core) Implement 'Print widget' option to print individual view sections.	2020-10-10 00:35:33 -04:00
server	(core) fix sync to s3 when doc is marked as dirty but proves to be clean	2020-11-10 08:12:31 -05:00
tsconfig.json	(core) move home server into core	2020-07-21 20:39:10 -04:00