* Fixes OracleAround so it creates unique oracle users
* Fixes rouge connection pool in JdbcLedgerDaoTransactionsSpec
* Fixes cleanup in OracleAroundAll
* Introduces lockIdSeed for test frameworks
* Adapts usage
changelog_begin
changelog_end
* damlc: Don't rely on polymorphic constant worker
Fixes https://github.com/digital-asset/daml/issues/12166 which was
caused by assuming that GHC would create a "worker function" for
all constructors. GHC doesn't create one if the constructor takes
no arguments. This only caused a problem with partially applied
constructors, so, it only applies to zero argument constructors of
polymorphic types in situations where the type argument is eta-reduced.
changelog_begin
changelog_end
* rename the test file
* Update compiler/damlc/daml-lf-conversion/src/DA/Daml/LFConversion.hs
Co-authored-by: Moritz Kiefer <moritz.kiefer@purelyfunctional.org>
Co-authored-by: Moritz Kiefer <moritz.kiefer@purelyfunctional.org>
In the split release process, the executable installer has to be created
later in the pipeline, once we have the Canton parts available.
CHANGELOG_BEGIN
CHANGELOG_END
We use tags to track releases; in particular, we want tags to correspond
to GitHub releases. In the split release process, the `assembly` repo is
responsible for creating GitHub releases, so it would make sense that it
is also the one responsible for creating tags.
I would also like to take this opportunity to manually remove all the
tags that have been created by the split release process so far and that
don't correspond to any release (which is all of them as we haven't done
a full split release yet), since they have already caused some
confusion.
CHANGELOG_BEGIN
CHANGELOG_END
* ledger-api-test-tool: Enable command deduplication tests by default.
CHANGELOG_BEGIN
- [Ledger API Test Tool] More command deduplication tests have been
enabled by default. This should not affect testing a fully functioning
ledger. If any tests fail, they can be temporarily excluded.
CHANGELOG_END
* Add an endpoint used for querying user rights of a specific user
changelog_begin
- [HTTP-JSON] Added endpoint /user/rights that if called with POST will return user rights of the user specified via the payload
changelog_end
* Add grant&revoke user rights endpoint
changelog_begin
- [HTTP-JSON] Added endpoints user/rights/grant & user/rights/revoke which allow granting & revoking user rights for a specific user
changelog_end
* Switch to using the UserRights list instead of a case class with fields
* fix type annotation
* Rename allocateUser func to createUser to comform with the endpoint path
* Response format simplification & cleanup
* Add one last test that ensure that the JSON format of UserRight doesn't change without us noticing
* Apply suggestions from code review
Co-authored-by: Stephen Compall <stephen.compall@daml.com>
* Remove unnecessary conversations and also just use unwrap for tagged strings
Co-authored-by: Stephen Compall <stephen.compall@daml.com>
I got unreasonably confused why we sometimes pass `Nothing` here and
why the templates are sometimes unused so this PR attempts to clarify
this a bit.
changelog_begin
changelog_end
withCreateProcess kills the server process but it doesn’t wait for it
to finish. The `typed-process` version does things properly here which
is also why we switched to it in other places.
changelog_begin
changelog_end
Continues the work started in https://github.com/digital-asset/daml/pull/12543
These libraries were only needed to transition from Scala 2.12 to 2.13
and are no longer useful as all the necessary items are now available
in Scala 2.13.
changelog_begin
changelog_end
* Add experimental Daml assistant support for ledger metering
CHANGELOG_BEGIN
Add experimental Daml assistant support for ledger metering
CHANGELOG_END
* Update with review comments
* Update with review comments
* Cut a new split release
I want one including the latest docs tweaks so I can pick them up in
the assembly repo.
changelog_begin
changelog_end
* bump to include msys fix
changelog_begin
changelog_end
Since Scala 2.13.2, Scala introduced built-in support to
manage warnings in a more granular fashion, thus making
the silencer plugin we are currently using no longer
strictly useful. Removing compiler plugins also removes
friction from migrating to Scala 3 in the future. As a
cherry on top, the built-in warning configuration also
allows to check whether a `@nowarn` actually does
anything, allowing us to proactively remove unused
warnings should the need arise.
[Here][1] is s a blog post by the Scala team about it.
Warnings have been either solved or preserved if useful,
trying to minimize the scope (keeping it at the single
expression scope if possible). In particular, all
remaining usages of the Scala Collection API compatibility
module have been removed.
Using the silencer plugin also apparently hid a few
remaining usages of compatibility libraries that were used
as part of the transition from Scala 2.12 to Scala 2.13
that are no longer needed. Removing those warnings
highlighted those.
changelog_begin
changelog_end
[1]: https://www.scala-lang.org/2021/01/12/configuring-and-suppressing-warnings.html
changelog_begin
[Java bindings] `DamlLedgerClient.forLedgerIdAndHost` and `DamlLedgerClient.forHostWithLedgerIdDiscovery` static methods
and the constructor taking a `ManagedChannel`, which were all deprecated since 0.13.38, have been removed.
changelog_end
* Upgrade to the latest Canton snapshot
Nothing super important that we need in there but I’d rather sync more
than less frequently.
changelog_begin
changelog_end
* .
changelog_begin
changelog_end
* .
changelog_begin
changelog_end
This fixes the timeout on trigger compat tests for the new sandbox (with LF >= 1.14).
The issue was that the trigger was "readAs"-ing with a party that
doesn't exist, since party ids aren't predictable with the new sandbox.
The solution is to allocate the Alice party ahead of time, and then
pass the allocated party in when calling `daml trigger`.
changelog_begin
changelog_end
changelog_begin
changelog_end
Fixes the transitive vulnerable dependency on `nanoid`.
Verified via `yarn audit`. Ran a quick manual test to check that
this did not break `navigator`.
* Upgrade msys2
We’ve seen some weird errors with outdated signatures and it seems
plausible that an upgrade may help.
changelog_begin
changelog_end
* .
changelog_begin
changelog_end
`alert` isn’t exactly great error handling but matches what we do in
other places of create-daml-app and I’m not all that keen on reworking
that everywhere for 2.0
fixes#12275
changelog_begin
changelog_end
* Adding minimal dynamic framework of independent DB migration unit testing
* Implementing (relevant parts of) PG 111 and 116 DB schema
* Adding test scenarios to test data migration for string interning and create-filter table population
changelog_begin
changelog_end
CHANGELOG_BEGIN
- [Ledger API Test Tool] The retired test suites, ``LotsOfPartiesIT``
and ``TransactionScaleIT``, have been removed in favor of more
targeted benchmarking tests. If you are actively including these tests
in your test run, you will need to remove them. These tests are
disabled by default so it is likely that no change will be needed.
CHANGELOG_END
* With mock metering service
* Reformat
changelog_begin
changelog_end
* Include nanos in generation time
* Update with review comments
* Update service count
* ledger-api-test-tool: Enable `ParticipantPruningIT` for everyone.
CHANGELOG_BEGIN
- [Ledger API Test Tool] The ``ParticipantPruningIT`` test case has
been enabled by default. You may need to disable specific test cases
accordingly.
CHANGELOG_END
run-full-compat: true
* Enable more ParticipantPruningIT tests across the board.
* ledger-api-test-tool: Exclude a multi-participant test by default.
The test, `PRImmediateAndRetroactiveDivulgence`, will now only run if
more than one participant is specified.
* ledger-api-test-tool: Use a `for` comprehension for readability.
Co-authored-by: tudor-da <tudor.voicu@digitalasset.com>
Co-authored-by: tudor-da <tudor.voicu@digitalasset.com>
I’ve kept it on the same test infrastructure that we used before that
can test both ways since it seems nicer to keep this consistent with v1.
changelog_begin
changelog_end
Breaks-protobuf: true
