Non managed version of party allocation. Use exclusively when testing the party management service.

Managed version of party allocation, should be used anywhere a party has to be allocated unless the party management service itself is under test

Creates a new user.

Additionally keeps track of the created users so that they can be cleaned up automatically when the test case ends.

Gets the absolute offset of the ledger end at a point in time.

Intended to be called by the infrastructure code after a test case's execution has ended.

Deletes a user.

Additionally keeps track of the created users so that they can be cleaned up automatically when the test case ends.

Create an EventFormat with a set of Party objects.

You should use this only when you need to tweak the request of transactions(request:com\.daml\.ledger\.api\.v2\.update_service\.GetUpdatesRequest):*, otherwise use the shortcut override that allows you to directly pass a set of Party

Returns an absolute offset (positive integer) that is beyond the current ledger end.

Note: the offset might not be valid for the underlying ledger. This method can therefore only be used for offsets that are only interpreted by the ledger API server and not sent to the ledger.

We are retrying a command submission + pruning to get a safe-to-prune offset for Canton. That's because in Canton pruning will fail unless ACS commitments have been exchanged between participants. To this end, repeatedly submitting commands is prompting Canton to exchange ACS commitments and allows the pruning call to eventually succeed.

Managed version of updateById(request:com\.daml\.ledger\.api\.v2\.update_service\.GetUpdateByIdRequest):* for topology transactions, use this unless you need to tweak the request (i.e. to test low-level details). If the parties list is empty then no filtering is applied to the topology transactions.

Managed version of updateByOffset(request:com\.daml\.ledger\.api\.v2\.update_service\.GetUpdateByOffsetRequest):* for topology transactions, use this unless you need to tweak the request (i.e. to test low-level details). If the parties list is empty then no filtering is applied to the topology transactions.

Managed version of updateById(request:com\.daml\.ledger\.api\.v2\.update_service\.GetUpdateByIdRequest):* for transactions, use this unless you need to tweak the request (i.e. to test low-level details)

Managed version of updateByOffset(request:com\.daml\.ledger\.api\.v2\.update_service\.GetUpdateByOffsetRequest):* for transactions, use this unless you need to tweak the request (i.e. to test low-level details)

Create a TransactionFormat with a set of Party objects.

You should use this only when you need to tweak the request of transactions(request:com\.daml\.ledger\.api\.v2\.update_service\.GetUpdatesRequest):*, otherwise use the shortcut override that allows you to directly pass a set of Party

Managed version of transactionTrees, use this unless you need to tweak the request (i.e. to test low-level details)

Managed version of transactionTreeByOffset

Non-managed version of transactions(request:com\.daml\.ledger\.api\.v2\.update_service\.GetUpdatesRequest):*, use this only if you need to tweak the request (i.e. to test low-level details)

Managed version of transactions(request:com\.daml\.ledger\.api\.v2\.update_service\.GetUpdatesRequest):*, use this unless you need to tweak the request (i.e. to test low-level details)

Non-managed version of transactions(request:com\.daml\.ledger\.api\.v2\.update_service\.GetUpdatesRequest):*, use this only if you need to tweak the request (i.e. to test low-level details)

Non-managed version of updateById(request:com\.daml\.ledger\.api\.v2\.update_service\.GetUpdateByIdRequest):*, use this only if you need to tweak the request (i.e. to test low-level details)

Non-managed version of updateByOffset(request:com\.daml\.ledger\.api\.v2\.update_service\.GetUpdateByOffsetRequest):*, use this only if you need to tweak the request (i.e. to test low-level details)