As requested by Martin in #8069, we extract most of the changes from
DecodeV1Spec in a separate PR.
This advances the state of #7155
CHANGELOG_BEGIN
CHANGELOG_END
* Add party management service to the services page, targeting #8027.
CHANGELOG_BEGIN
CHANGELOG_END
* rephrase to make it more compact
Co-authored-by: Bernhard Elsner <40762178+bame-da@users.noreply.github.com>
* remove unnecessary note
Co-authored-by: Bernhard Elsner <40762178+bame-da@users.noreply.github.com>
* remove unnecessary note
Co-authored-by: Bernhard Elsner <40762178+bame-da@users.noreply.github.com>
* remove blank line
Co-authored-by: Bernhard Elsner <40762178+bame-da@users.noreply.github.com>
A question on discuss prompted me to read this page, and I spotted a
couple typos.
As a side note, I find references to DAML-LF versions unhelpful. I don't
think it's fair to expect our users to know the mapping between DAML
versions and DAML-LF versions.
CHANGELOG_BEGIN
CHANGELOG_END
* Use `WriteConfigService` in LedgerConfigProvider.
* Write unit tests for LedgerConfigProvider.
CHANGELOG_BEGIN
CHANGELOG_END
* Use explicit configurations in LedgerConfigProviderSpec.
* Support multiple submitters in kvutils protobuf
CHANGELOG_BEGIN
CHANGELOG_END
* Sort submitters for the deduplication key
* Apply suggestions (style)
* Add test for command deduplication keys
Having the cron push artifacts to GCP was really only meant to happen
once. I got distracted and worked on other things. This PR closes that
work loop such that the current state and expectations are:
- Every new release pushes to GCP as part of the release process.
- The cron only checks that the GCP backup exists and matches, but does
not push if it doesn't.
The reason for this is we want the cron job to fail if there are
additional, unexpected files in a release, rather than automatically
commit those files for the long term.
CHANGELOG_BEGIN
CHANGELOG_END
Addresses security advisory. I upgraded typedoc as well since that
pulls in the older version of highlight.js and I dont like breaking bounds.
changelog_begin
changelog_end
* Link concepts "gRPC Ledger API" and "Ledger API" in glossary for #8029.
CHANGELOG_BEGIN
CHANGELOG_END
* remove gRPC Ledger API which was in the wrong place
* rephrase alternative names
Co-authored-by: Bernhard Elsner <40762178+bame-da@users.noreply.github.com>
Co-authored-by: Bernhard Elsner <40762178+bame-da@users.noreply.github.com>
This is the macOS part of #5912, which I have separated because our
macOS nodes have a different deployment process so it seemed easier to
track the deployment of the change separately.
CHANGELOG_BEGIN
CHANGELOG_END
This addresses feedback on the upgrade documentation. We switch the
example from coins to carbon certificates and add a section for the
centralized database case to make the base case clear.
CHANGELOG_BEGIN
CHANGELOG_END
Adds TLS certificates revocation checking in the LedgerApiServer using the OCSP.
The feature is implemented by setting global JVM properties.
Integration tests for the new feature include spinning up a local OCSP responder using the openssl command.
CHANGELOG_BEGIN
- new CLI option --cert-revocation-checking for enabling the TLS certificate revocation checking in the LedgerApiServer
- documentation about the new feature
CHANGELOG_END
@cocreature is taking care of 1.8.0-snapshot.20201124.5709.0.dabd55d0 (#8055), so they get pushed back to the end of the line.
Please do not merge this before #8055.
CHANGELOG_BEGIN
CHANGELOG_END
Co-authored-by: Azure Pipelines DAML Build <support@digitalasset.com>
* Upgrade akka-http to 10.2
Follow up to #8048, I left out this upgrade to reduce noise and since
I wasn’t quite sure how involved it was going to be.
changelog_begin
changelog_end
* Reenable transparent HEAD requests
Apparently no longer on by default but we depend on this in waitForHttpServer
changelog_begin
changelog_end
CHANGELOG_BEGIN
kvutils reports LookupByKey node mismatches during validation as Inconsistent
instead of Disputed if they can be due to contention on the contract key
CHANGELOG_END
This PR has been created by a script, which is not very smart and does not have all the context. Please do double-check that the version prefix is correct before merging.
@cocreature is in charge of this release.
CHANGELOG_BEGIN
CHANGELOG_END
Co-authored-by: Azure Pipelines DAML Build <support@digitalasset.com>
* Upgrade akka and akka-http
Was chasing an issue somewhere and thought this might affect it in
some way. It didn’t but I might as well turn the upgrade into a PR.
changelog_begin
changelog_end
* Fix trigger service tests
changelog_begin
changelog_end
* Downgrade akka-http again
changelog_begin
changelog_end
* Upgrade akka-http again and fix tests
changelog_begin
changelog_end
* Cleanup trigger service
changelog_begin
changelog_end
* Refactor indexing to minimize transaction traversals
changelog_begin
[Integration Kit] Bugfix: daml.index.db.store_transaction metrics were keeping track of empty insertions, skewing down the numbers
[Integration Kit] Performance: minimizing the number of traversals of a transaction to index it, more efficient indexing
changelog_end
* Add empty stakeholders for non-consuming exercises
* Fix test to check usage of pre-computed blinding info
* Remove unnecessary string interpolators
* Shorten creation of net visibility
* Delete obsolete comment
* Add visibility of divulged contracts
* Address review https://github.com/digital-asset/daml/pull/8019#discussion_r527666572
* Address review https://github.com/digital-asset/daml/pull/8019#pullrequestreview-535399441
* Address review https://github.com/digital-asset/daml/pull/8019#discussion_r527681774
* Fix ordering of batches, use explicitly named types to avoid confusion
* Default to an empty set if a divulged contract is not visible in the current transaction
* Shorten references to store transaction metrics when writing
* Address review https://github.com/digital-asset/daml/pull/8019#discussion_r527745640
* Add divulgences from past transactions
* More fine-grained types and signatures
* kvutils/tools: Factor out builds from IntegrityCheckerSpec.
* kvutils/tools: Verify that write sets are readable.
CHANGELOG_BEGIN
- [Integration Kit] The integrity checker now validates the contents of
each write set, regardless of whether it is used subsequently.
CHANGELOG_END
* kvutils/tools: Move the write set exception outwards.
* kvutils/tools: Make the integrity checker `main` method easier to read.
* kvutils/tools: Move `WriteSetEntries` logic into CommitStrategySupport.
This makes it more flexible with regards to extended write sets.
* kvutils/tools: Use the support state key serialization strategy.
* Participant pruning ledger api server support ported from Canton
CHANGELOG_BEGIN
- [Ledger API]: The preview of `ParticipantPruningService` enables ledger participants to prune the "front" of ledger state at the participant including the ledger api server index.
CHANGELOG_END
* Review feedback from Stefano
* Add pruning tests plus missed command completions change
* Review feedback from Robert
* Improved test readability by having populate helper return offsets
* Review feedback
* Ledger api changes to pruning api and disable canton pruning test
- Change return result to PruneResponse
- Change type of PruneRequest.prune_up_to to string
* Review feedback: Use ApiOffsetSConverter for logged offsets
* kvutils/tools: Fix the integrity checker so it compares state updates.
Previously, it would always take the list of updates _before_ processing
the import, leading to this useless check:
Comparing expected and actual state updates.
Successfully compared 0 state updates.
This makes the snapshotting lazy (by using a function instead of a
value), ensuring we actually perform the assertion.
CHANGELOG_BEGIN
CHANGELOG_END
* kvutils/tools: Add a test for the state updates regression.
The stream from the JSON API is split into two sections:
1. The unordered section of ACS events.
2. The ordered transaction stream after the live event.
Our assertions assume that we only get 2 but currently we don’t wait
before sending commands so depending on timing, some of the events can
be delivered as part of the ACS section in a different order causing
very confusing assertion failures.
This test fixes this by waiting for the live event indicating the end
of section 1 and thereby forcing everything to come via the ordered
transaction stream.
Verified that this fixes the flakiness with --runs_per_test=50 which
reproduced it fairly reliable before (on CI, never managed to hit it
locally).
changelog_begin
changelog_end
Add a description of how to enable LaTeX input mode when editing the
DAML-LF spec in VS Code. Also add some additional symbols.
CHANGELOG_BEGIN
CHANGELOG_END
* Test and fix Conversions#encodeBlindingInfo
* Fix rebase
* Read and prefer pre-computed blinding info when decoding KV transaction log entries
CHANGELOG_BEGIN
CHANGELOG_END
* Fix rebase
* Tidy up
* Tidy up
* Fill DamlTransactionEntry#bindingInfo during TransactionCommitter#blind
CHANGELOG_BEGIN
CHANGELOG_END
* Test and fix Conversions#encodeBlindingInfo
* Fix rebase
* Fix non-determinism
* Reduce visibility
* Tidy up
* Do not backpressure from the command tracker output to the submission flow.
This is required to meet the contract of CommandClient.trackCommandsUnbounded, which allows for submitting an unbounded number of commands.
This is in turn required to use CommandClient.trackCommandsUnbounded as part of a flow that retries (some of the) failed command submissions.
CHANGELOG_BEGIN
CHANGELOG_END
* Revert "Do not backpressure from the command tracker output to the submission flow. This is required to meet the contract of CommandClient.trackCommandsUnbounded, which allows for submitting an unbounded number of commands. This is in turn required to use CommandClient.trackCommandsUnbounded as part of a flow that retries (some of the) failed command submissions."
This reverts commit 20c0b8e3
* Adding a disclaimer to the CommandClient so that users are not totally surprised about unexpected backpressure.
