* Extracted kvutils Config to //leger/ledger-runner-config
changelog_begin
changelog_end
* Sandbox-on-X logback.xml does not depend on the kvutils/app one
* Remove unused dependencies
* Add copyright header back
* Remove dependency of SoX on kvutils
I tried to keep the changes somewhat minimal and reuse what is already
there. I think there is a fair amount of cleanup we can do afterwards
but hopefully this way it’s easier to review.
fixes#12837
changelog_begin
- [Daml Script] `daml test-script` has been replaced by `daml script
--all`. The option to spin up a ledger automatically has been
removed and you always have to specify one.
changelog_end
@ray-roestenburg-da is taking care of testing 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>
* Move //ledger/ledger-api-test-tool to //ledger/ledger-api-tests/tool.
And conformance.bzl to //ledger/ledger-api-tests.
* Move test tool infra to //ledger/ledger-api-tests/infrastructure.
* Split the ledger API test tool into smaller libraries.
There is no change to behavior.
CHANGELOG_BEGIN
CHANGELOG_END
* ledger-api-tests: Encapsulate performance tests.
* ledger-api-tests: Extract a "runner" library.
* ledger-api-tests: Publish libraries to Maven Central.
* ledger-api-tests: Fix Scaladoc so it compiles correctly.
Unfortunately I had to remove some Scaladoc in ActiveContractsServiceIT
which is incorrectly interpreted as not being attached to anything.
Fortunately, it's not actually that helpful.
* compatibility: Fix paths to the Ledger API Test Tool.
* Fix release types for ledger API test libraries.
* test-common: Publish generated Scala.
These libraries are dependencies of the ledger API tests components.
* ledger-api-tests: Use "com.daml" as the group ID everywhere.
* ledger-api-tests: Check that tests in `--additional` are valid.
* compatibility: Fix a reference to ledger-api-test-tool I missed.
specifying a non-existent logback file is apparently not an error and
just silently produces garbage.
Probably should add a test that checks all logback files for existent
but that seems somewhat convoluted to setup so I’p prefer to skip that
for now.
changelog_begin
changelog_end
I suppose whoever fixed this forgot to update these instructions, but as of `2.0.0-snapshot.20220204.9165.0.225c58f4` I observed well-formed "Bob" and "Alice" values in the messaging dropdowns.
@adriaanm-da is taking care of 2.0.0-snapshot.20220201.9111.0.53905056 (#12703), so they get pushed back to the end of the line.
Please do not merge this before #12703.
CHANGELOG_BEGIN
CHANGELOG_END
Co-authored-by: Azure Pipelines Daml Build <support@digitalasset.com>
Depends on #12716 and #12625 (CI fails until they are merged & this
is rebased so no chance of merging this accidentally).
changelog_begin
changelog_end
* Upgrade to Scala 2.13.8
changelog_begin
changelog_end
* Update hash for scala in nixpkgs
* update more hashes for scala upgrade
* Fix most warnings etc.
* Fix remaining errors etc.
* Fix formatting
* Resolve last errors hopefully
* Fix ledger api common build file
* Combine imports & revert accidental change that broke the CI run
* Rename exporting vals to scriptExport & minimize diff
* Remove more wrong changes
* moved warning around
The issue with the message dropdown looking like garbage will
obviously be fixed. Just trying to reflect the current state.
changelog_begin
changelog_end
This could not be achieved previously due to an issue that has
been fixed by https://github.com/DACH-NY/canton/pull/8475.
The next release should be tested again with the Canton-based
sandbox to ensure it works on both Windows and MacOS/Linux.
changelog_begin
changelog_end
The Canton sandbox currently has a startup issue that
has to be fixed that causes an unusually long startup
time on Windows that ends up triggering a timeout.
Can be reverted once https://github.com/DACH-NY/canton/issues/8331
is fixed.
changelog_begin
changelog_end
* Remove reset service from grpc and documentation [DPP-804]
CHANGELOG_BEGIN
Remove reset service from the ledger api protocol and the documentation
CHANGELOG_END
* remove reset service from two left-over places
* remove reset service from the protobuf structure test
@garyverhaegen-da is taking care of 2.0.0-snapshot.20220118.8919.0.d0813e61 (#12467), so they get pushed back to the end of the line.
Please do not merge this before #12467.
CHANGELOG_BEGIN
CHANGELOG_END
Co-authored-by: Azure Pipelines Daml Build <support@digitalasset.com>
* Make quickstart-java template work with canton
Also update the quickstart-java release test instructions to use the new sandbox. This is a bit more involved than before, because of the party names being different every time, but I hope this is not too much of a burden. The test here is similar to what gets tested in the assistant integration test for quickstart-java.
changelog_begin
changelog_end
* try to fix indentation
And change the relevant release test instructions to make it clear this
isn't a quickstart-java project, but a project that uses the default
template (skeleton).
changelog_begin
changelog_end
Was a bit too eager in the last PR, and changed the release test to use
`daml start` instead of `daml start --sandbox-kv`. This PR reverts this
until we make create-daml-app work with the new sandbox.
changelog_begin
changelog_end
* Change default sandbox to canton.
Some progress on #11831
* made `daml start` use canton sandbox by default
* changed the non-ledger api ports to use free ports by default
(still haven't tried using port 0 instead of `getFreePort`).
* renamed `daml sandbox-canton` to `daml sandbox`
* implement a `--static-time` option for `daml sandbox` that sets the
canton clock type parameter to `sim-clock`
* moved the quickstart-java integration test to use the new sandbox
* the test uses `--static-time`, but doesn't really depend on it
changelog_begin
changelog_end
* fix parens
* fix hot reload test
* reinstant --sandbox-kv in create-daml-app test for now
* fix damlStart test
NodeJS 12 is eol in April and there are already packages (e.g. vsce)
that dropped support. We probably should upgrade even further but for
now I’m going with the most conservative approach.
changelog_begin
changelog_end
* Rename daml sandbox to daml sandbox-kv
Also drop the default sandbox on `daml start`
Part of #11831
changelog_begin
changelog_end
* update release test instructions
* try to fix a couple compat tests
* dont need special 0.0.0 logic
* buildifier-fixx
* Drop `platform-version` support from `daml.yaml`
Doesn’t work properly with Canton sandbox, nobody uses it and product
agreed to deleting it.
changelog_begin
changelog_end
* drop run-platform-jar
changelog_begin
changelog_end
* fix run-jar commands
changelog_begin
changelog_end
* Add report metering protobuf definition
changelog_begin
Added experimental GRPC endpoint for the reporting of metering
changelog_end
* Update with review comments
* add changes from joint review by Simon and Simon :D
* Update with review comments
* Update with review comments
Co-authored-by: Simon Meier <simon@digitalasset.com>
We messed that up in the past and lost the hierarchical structure so
adding a test seems reasonable and these change sufficiently rarely
that updating it isn’t an issue.
changelog_begin
changelog_end
@stefanobaghino-da is taking care of 2.0.0-snapshot.20220104.8767.0.d3101e01 (#12263), so they get pushed back to the end of the line.
Please do not merge this before #12263.
CHANGELOG_BEGIN
CHANGELOG_END
Co-authored-by: Azure Pipelines Daml Build <support@digitalasset.com>
New year, new copyright, new expected unknown issues with various files
that won't be covered by the script and/or will be but shouldn't change.
I'll do the details on Jan 1, but would appreciate this being
preapproved so I can actually get it merged by then.
CHANGELOG_BEGIN
CHANGELOG_END
@cocreature is taking care of 2.0.0-snapshot.20211214.8692.0.63940872 (#12147), so they get pushed back to the end of the line.
Please do not merge this before #12147.
CHANGELOG_BEGIN
CHANGELOG_END
Co-authored-by: Azure Pipelines Daml Build <support@digitalasset.com>
We didn’t have any artifacts there since SDK 1.0 and we’re not
planning to add any. We suspect that the permission denied errors
might come from the fact that we need a different profile id for that
and while we don’t use the repo to upload anything we still create the
staging repo so this might fix that issue.
changelog_begin
changelog_end
* Remove Extractor
Extractor is being removed after a long time being in Labs status.
This should improve the flakiness on CI.
🔥
changelog_begin
Extractor has been removed from the SDK
changelog_end
* Remove Extractor documentation
* Remove Extractor from CODEOWNERS
* Remove Extractor references in Daml-LF build files
* Remove Extractor references in the Daml SDK assistant
* Remove Extractor from the SDK
* Remove Extractor reference from CONTRIBUTING.md
* Get rid of deprecated components
Removes:
- mentions of the Node.js bindings
- mentions of the Scala bindings
- usage of the Scala codegen as an SDK tool
- Java bindings "reactive components"
changelog_begin
The Node.js bindings are no longer supported as part of the Daml SDK
The Scala bindings are no longer supported as part of the Daml SDK
The Java bindings reactive components are no longer supported as part of the Daml SDK
The `daml codegen` command has dropped support for Scala
changelog_end
* Fix typo noticed by @cocreature
Co-authored-by: Moritz Kiefer <moritz.kiefer@purelyfunctional.org>
* Address https://github.com/digital-asset/daml/pull/12167#issuecomment-995714093
* Remove quickstart-scala from the SDK tarballs
* Fix failing codegen test
* Address https://github.com/digital-asset/daml/pull/12167#pullrequestreview-833991243
Co-authored-by: Moritz Kiefer <moritz.kiefer@purelyfunctional.org>