* _tryCatch sig
* CatchPayload now only continues via 'continue' field
* fmt
* Add test cases
* update docs for CatchPayload
* fix type of CatchPayload.continue
* Add x type parameter to CatchPayload, drop toLedgerValue
This PR adds the attributes createArgumentsBlob and ContractMetadata to the CreatedEvent types by the Java bindings.
Passing these attributes through is required for being able to use explicit disclosure with the Java bindings (required by the CN team).
* bump canton to 20230202
CHANGELOG_BEGIN
CHANGELOG_END
* DACH-NY/canton#11206 Fix dev option flags for Canton in `ledger-api-test-tool-on-canton`
---------
Co-authored-by: Azure Pipelines Daml Build <support@digitalasset.com>
Co-authored-by: Kirill Zhuravlev <kirill.zhuravlev@digitalasset.com>
A concern with the existing pruning backend tests is that they are relatively complex particularly because:
- in order to fetch data from the indexdb they use production sql queries which might have builtin knowledge of pruning offsets,
- production sql queries are not designed for ergonomic one-off usage.
This PR introduces a set of queries, one for each table subject to pruning, each returning a record for each row its table. This leads to more a concise and straightforward way assert what data has or hasn't been pruned.
* Common metrics reporter config format
Fixed the config for metrics reporter for trigger service and oauth
middleware.
They are using a common config definition, as well as the JSON API
service.
The format matches the one used in canton configs.
CHANGELOG_BEGIN
CHANGELOG_END
* Add rules for running single scenarios, redefine RunScenario using them
* Turn runScenario into an action, not IO
* Add FormattingStarted custom message type
* Redefine OfInterest rule in terms of RunSingleScript
* lint
* fix broken renamed var
* Use getFilesOfInterest for diagnostics & uncompilable check
* explicitly run tests that need to be run
* Amend test
* Remove commented out code
* Remove vr formatting message
@dylant-da is taking care of [testing](https://github.com/digital-asset/daml/blob/main/release/RELEASE.md) today's release, so they get pushed back to the end of the line.
Please do not merge this before the release is fully tested.
CHANGELOG_BEGIN
CHANGELOG_END
Co-authored-by: Azure Pipelines Daml Build <support@digitalasset.com>
Previously the config key `index-service.events-processing-parallelism` was used both when fetching ACS from DB
and for buffered transaction reader.
Now these resposibilities are separated into two new config keys:
1. `index-service.acs-streams.contract-processing-parallelism` (which mirrors the tx streams configs)
2. `index-service.buffered-events-processing-parallelism`
Also moving a larger chunk of code from TransactionReader to ACSReader (which mirrors the tx stream readers)
* confirm that monadifying the package fetch still suppresses the error
* thread ExecutionContext from request
- makes the error less likely
- but still fairly easy to repro with 3 tabs
* experiment with setting executor
* explain that the cache isn't a cache
* random order, maybe
- #3090 mentions keeping the order as a goal; I don't see why we should,
though
* random order with groups of 8
* embed the decoding
- this slows down the processing of a group, yielding somewhat less
granular contention
- and also makes hits cost much less, at the cost of making granular
contention more expensive
* reduce diff size before resolution
- this won't improve contention, but does nearly eliminate the cost of
resolution for already-resolved packages, making hits nearly free
(amortized)
* randomize groups instead
- while groups themselves can overlap with this arrangement, each
costing ParallelLoadFactor granular contention, on average it seems to
perform a little better due to groups never overlapping
* refactor StatusEnvelope to utils
* constant 250ms retry
* detect contention earlier and skip decode
* factor traverseFM
