Since https://github.com/digital-asset/daml/pull/17989
A simple heuristic to remind you to consider adding `run-all-tests: true` to your commit message if making changes in corners of the codebase most likely affected.
* Rename //bazel_tools:match-{cabal=>golden}-file
* Generate and check hash file for contents of //compiler/damlc/tests:platform-independence.dar
* Add pre-commit hook to test //compiler/damlc/tests:platform-independence-dar-hash-file-matches
* Print info when //bazel_tools:match-golden-file fails
* platform-independence-dar-check pre-commit hook runs depending on env var
* Skip platform-independence-check if RUN_PLATFORM_INDEPENDENCE_CHECK is unset
* Document dar_hash_file rules
* move platform-independence-checks warning to .envrc
* implement generate_dar_hash_file genrule in python
in particular, this allows us to produce the same output on all platforms
* fix windows
* Update rules_daml/daml.bzl
* bytes.replace does not operate in place
* Resolve release version for sdk build checks
* lint
* lint
run-full-compat: true
* Simple test for using daml-script in release versions
* Fix build issues in tests using pSdkVersion
run-full-compat: true
* Fix build issues with DamlcIntegration
* fix bad sdk version being an invalid version
run-full-compat: true
* Fix the linux "mmap 4096 bytes at (nil): Cannot allocate memory" error
* Fix compat tests on Windows
run-full-compat: true
* test windows os correctly
run-full-compat: true
* temporarily disable canton_3x
run-full-compat: true
---------
Co-authored-by: Paul Brauner <paul.brauner@digitalasset.com>
* build canton 3.x in build.yml
* Apply suggestions from code review
Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>
* Apply suggestions from code review
Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>
* apply suggestions
---------
Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>
Basically we remove the dependency of different components on "//language-support/scala/bindings" by:
- replacing com.daml.ledger.api.refinements.ApiTypes.Party by com.daml.lf.data.Ref.Party
- replacing com.daml.ledger.api.refinements.ApiTypes.ApplicationId by Option[com.daml.lf.data.Ref.ApplicationId] (here we use option as ApiTypes.ApplicationId allows empty string while Ref.ApplicationId does not).
- adding rounding logic for timestamp in com.daml.lf.data.Time.Timestamp and use it instead of the one from com.daml.api.util.TimestampConversion
Note we did not clean daml-sript export as it have never pass the alpha stage and will be dropped with the 3.x fork.
* Add --install-with-custom-version, rename --allow-install-non-release
* Test install tarball via custom version in compatibility tests
run-full-compat: true
* do not run pr-only tests on main, do not run main-only tests on prs
* split data dep tests into main-only and pr-only
* run non-dev conformance tests on main only
This means that if a websocket query is initiated with an explicit offset, and the ledger returns an error reporting that the offset has been pruned, the websocket query will be terminated with an error containing a status of `410` (Gone) and a message indicating that the offset has been pruned.
The client will need to react to this by clearing any state that had been incrementally built based on updates, and refresh with current version of ledger state.
This is related to https://github.com/digital-asset/daml/issues/13788 and https://github.com/digital-asset/daml/issues/13680
As discussed there, the existing akka APIs do not support setting the websocket close code and reason. The approach taken here is to return a single message with a custom error and close the websocket.
