Moritz Kiefer 4e1c5fedb3 Check visibility for by-key operation of local contracts (#9470) ... * Check visibility for by-key operation of local contracts fixes #9454 I tried out two approaches for this: 1. The one here where we add a new callback. This has the advantage that the engine remains oblivious to visibility checks. They are all done outside and the engine doesn’t even know about the reading parties. 2. Make the engine aware of the reading parties. A start of that is in #9458. Both work in principle but I ended up going for 1 in the end. Doing half of the visibility checks outside the engine and half inside just seems worse than the current state. changelog_begin - [Daml Engine] Fix a bug where it was possible to fetch/lookup/exercise a local contract by key even if the reading parties are not stakeholders. See #9454 for details. changelog_end * Disable new test on Canton changelog_begin changelog_end * Exclude from compat tests changelog_begin changelog_end * s/LocalLookup/LocalFetch/ changelog_begin changelog_end * Address review changelog_begin changelog_end		2021-04-22 21:39:12 +02:00
..
bootstrap.canton	Reenable multi-node ledger-api-test-tool conformance test against Canton (#6449)	2020-06-23 09:06:28 +02:00
BUILD.bazel	Check visibility for by-key operation of local contracts (#9470)	2021-04-22 21:39:12 +02:00
canton-test-runner.sh	Update canton tests to pre 0.23.0 release (#9356)	2021-04-08 13:53:49 +02:00
canton.conf	Upgrade canton to 0.21.0 which supports lf-version 1.11 (#8963)	2021-02-26 16:52:03 +00:00
enable-faster-pruning.conf	Participant pruning ledger api server support ported from Canton (#7988)	2020-11-23 15:28:04 +01:00
logback-debug.xml	Canton conformance test debug logging and reduced test parallelism (#7322)	2020-09-04 14:25:30 +02:00
unique-contract-keys.conf	Upgrade ledger-api-test-tool-on-canton to the canton 0.19.0 release (#7931)	2020-11-10 18:09:58 +01:00