* add an lf-major-version flag to the repl service and pass it from the haskell client
* test LF2 in the daml-repl tests
* formatting
* formatting
* remove obsolete TODO
* fix //compiler/damlc/tests:repl
* port repl-functests to LF v2
* do not assume that LFV2 => dev
* address Moises' comments
* Add failing tests
"'bank' fetches" should be "'alice' fetches" in the ledger output when 'alice' is the divulging party
* Handle fetch node actors correctly in scenario-service
* Handle fetch node actors correctly in lf-interpreter pretty printer
In doing so, we disable the automatic production of the extra reports from gatling results.
These can be re-enabled in future if they're considered valuable.
We are already checking for activeness when we insert are a Fetch or an Exercise
node, for consistency we add the check when inserting Lookup node.
Note that, as for the Fetch and Exercise node, this is a sanity check, the engine
should never try to insert a successful lookup node for a contract that is inactive
* pin dependencies to json and add missing dep
* fix cyclic dep
* remove unused dep
* add missing dep to //ledger-api/testing-utils:testing-utils
* remove unused dep in //ledger/ledger-api-auth:ledger-api-auth
* remove more unused deps
* more dep fixes
* yet more dep fixing
* more fixing..
* more of the same
* hopefully the last deps to fix
* Bump the version of protobuf and fix everything that depends on it. Took shortcuts that I need to fix in a next commit, but would like to run the CI on this now that it compiles
* don't error out in the grpc-haskell patch
* remove obsolete patch
* patch absl to compile on mingw
* Add a patch to recognize the compiler
* Define _DNS_SD_LIBDISPATCH for macOS gRPC
* bump netty_tcnative_version according to https://github.com/grpc/grpc-java/blob/master/SECURITY.md#netty
* pin maven deps
* Fix macos linking errors 'dyld[xxx]: missing symbol called'
* Skip Darwin frameworks in package-app.sh
* pin stackage packages
* pin stackage windows deps
* use the netty version agreed on
* bump the windows global cache to try and debug the upb issue
* restart the CI after timeout
* clean up
* disable failing tests for now
* comment out unused code
* reset the windows machine name to 'default'
---------
Co-authored-by: Moisés Ackerman <6054733+akrmn@users.noreply.github.com>
* Add warnings to Gamma
* Warn instead of error for changed template expressions
* lint
* Errors and warnings for key types
* add context to warnings where relevant
* Add warning logic to DamlcUpgrades, fix errors that are now warnings
* Add tests for key errors and warnings (signatories, expression, type)
* Refactor expression extraction, fix extract key expression/maintainers
* satisfy lint, trigger test restart
* Test error for dropped key and warning for added key
* Warn for extraction issue instead of erroring out
* Change `cannot change` error-wording with `has changed` warning-wording
* comments for extractors
* Revert "Add SharedGlobalKey"
This reverts commit 6592cb7bd5.
* Adding shared flag to GlobalKey
* Remove shared flag from GlobalKey
* Support old and new grcp error parsing
* Add tests for hashContractKey
Turns out some people depend on it. I still think they shouldn't, and we
should work with them to help them move away, but short-term the right
thing to do is to not block their upgrade.
* Implement vetDar and unvetDar
Blocked by canton not returning uploaded dars
* Upgrades testing infra/IT
* Fix HttpServiceTestFixture
* Fix some tests
* Fix cantonRunner for windows
* Add delay after vet actions so topology transactions can land
* Implement invalid data upgrades tests
* Add temporary internal setContractUpgradingEnabled flag to daml-script
* Switch to setProvidePackageId
* Write choice and multi-participant tests
* Formatting
* Remove unused import
* Address reviews
* Update errors
* Fix canton runner for windows
* Address review comments
* Add new proto to artifacts
* avoid pushing canton admin proto as maven artifact (#17742)
---------
Co-authored-by: Remy <remy.haemmerle@daml.com>
By the way, I don't have any special powers here. I'm just running:
```
./release.sh snapshot 42581f2961 2.8.0
```
and putting the result at the top of the `LATEST` file.
* Adapt JSON API write path to the new explicit disclosure Ledger API interface
* Address review comments
* Switch to vanilla Base64 for createdEventBlob instead of Base64Url
* update TypeScript bindings of DisclosedContract to use the createdEventBlob field instead of payload, payloadBlob and metadata, and short-circuit a test which depends on canton populating the createdEventBlob field
* get TypeScript integration tests to use transaction service to get created_event_blob data
---------
Co-authored-by: = <=>
