mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 01:07:18 +03:00
1c4f173f3a
* Always use max_deduplication_duration as deduplication period for committer side deduplication Doing this we get the following guarantees: - Deduplication period is constant for all the submissions therefore this guarantees consistency between "backward-looking" and "forward-looking" deduplication CHANGELOG_BEGIN kvutils - committer side deduplication always uses max_deduplication_duration + min_skew as a deduplication period for all the requests. CHANGELOG_END * Set max_deduplication_duration to 10 seconds for all the conformance tests * Update KV command deduplication conformance tests to account for max deduplication duration used as deduplication period for all the requests * Add max deduplication wait for multi-participant conformance test * Overwrite the submitter info deduplication period in the transaction committer so that we always set the max deduplication duration * Update ledger/participant-state/kvutils/src/test/suite/scala/com/daml/ledger/participant/state/kvutils/committer/transaction/TransactionCommitterSpec.scala Co-authored-by: Miklos <57664299+miklos-da@users.noreply.github.com> * Add separate step for overwriting the deduplication period * Code review - reformatting and renames * Add comment for setting the deduplication duration |
||
---|---|---|
.. | ||
jdbc-drivers | ||
non-repudiation | ||
non-repudiation-api | ||
non-repudiation-app | ||
non-repudiation-client | ||
non-repudiation-core | ||
non-repudiation-perf | ||
non-repudiation-postgresql | ||
non-repudiation-resources | ||
non-repudiation-testing |