* Don't allow starting a participant with Postgres major version < 10
CHANGELOG_BEGIN
- [Integration Kit] - a participant cannot be run with Postgres versions <10
CHANGELOG_END
* Add a test
* Fix the test case to work on Windows where we use Postgres 12
* Add Oracle compatibility tests
changelog_begin
changelog_end
* Clean up
* Remove debug change
* Skip Oracle tests if there is nothing to do
* Add missing line warp
* Use ORACLE_PORT
Co-authored-by: mziolekda <marcin.ziolek@digitalasset.com>
Co-authored-by: mziolekda <marcin.ziolek@digitalasset.com>
In docs:
* doc that we require Java 11, not 8
In release instructions:
* mention everywhere that all-lowercase party entries should be made
* wrong line number for variable go-to-defn check
CHANGELOG_BEGIN
CHANGELOG_END
* Do not require Ledgers to implement UserManagementService when using with ledger-api-bench-tool.
CHANGELOG_BEGIN
CHANGELOG_END
* Minor refactor
* Improve comments and code structure for the regular user setup step
* Fix the completions authorization assertion
Complements #12952 which drops it from create-daml-app by also
dropping it from the rest.
Couldn’t find any docs or other stuff that is broken by this.
changelog_begin
changelog_end
* ledger-api-tests: Remove the performance-testing functionality.
This has been superseded by the Ledger API Bench Tool.
CHANGELOG_BEGIN
- [Ledger API Test Tool] The performance tests have been removed from
this tool, in favor of the Ledger API Bench Tool, which is much more
capable and configurable.
CHANGELOG_END
* ledger-on-sql/sandbox-on-x: Stop running performance tests.
We don't check the results anyway.
... so that Navigator shows users for login by default.
When parties are specified explicitly in daml.yaml,
navigator uses those instead of querying user management
for the list of users a user can log in as.
These days, it actually doesn't make sense to list the
parties in the daml.yaml. Navigator will query party
mgmt for a list of known parties. We don't implicitly
allocate parties (anymore), so unclear why this section
is still here.
The users for the template are created by the init script
(see Setup.daml).
See #12945
CHANGELOG_BEGIN
CHANGELOG_END
* ledger-on-(memory|sql): Stop publishing to Maven.
Nothing depends on these any more.
We plan on removing them entirely, but for now we can just make sure
they're not published.
CHANGELOG_BEGIN
CHANGELOG_END
* Changelog.
CHANGELOG_BEGIN
- [Maven] Two internal components, "ledger-on-memory" and
"ledger-on-sql", are no longer published to Maven Central. If you were
relying on these components to implement a simple ledger, we encourage
you to migrate to the community edition of Canton.
CHANGELOG_END
This is completely unmaintained, unused and partially broken so delete
it for now. Worst case, we recover it from Git history.
closes#6550 because it now refers to deleted code.
changelog_begin
changelog_end
We needed this before the upgrade to GHC 9.0 due to our use of
integer-simple. With GHC 9.0 and the corresponding switch from
integer-simple to ghc-bignum native this is no longer required.
changelog_begin
changelog_end
I also changed CI config so we run this on every build but only upload
on releases. That should hopefully make sure we catch this immediately
next time. The script is fast enough that this shouldn’t slow this
down meaningfully.
changelog_begin
changelog_end
Trying to work around https://github.com/akka/akka/pull/30944/files
having introduced rather confusing log messages in Daml script.
There are probably some other tools where we might want to do this but
I think daml script is the main one as the other ones are long-running
services where you don’t expect to shutdown the actor system during
regular operatino.
changelog_begin
changelog_end
Fixes#12789
Adds a new query endpoint to Navigator's GraphQL backend that
lists all the parties registered by Navigator. The parties are
filtered on the server based on a query from the frontend and
served back. The frontend uses this to provide suggestion and
autocompletion features whenever a party identifier input is
required.
changelog_begin
[Navigator] Whenever you have to input a party identifier you
are now offered suggestions and the possibility to
autocomplete. See #12789.
changelog_end
Since #12645, we added a new pipeline, so we need to add a corresponding
entry.
As for #12645, the content of the files and the directory structure is
taken directly from a live CI node, as printed by the (now-named)
`workdirs` step.
CHANGELOG_BEGIN
CHANGELOG_END
* Support building via rosetta
Not as nice as a native build but seems useful enough until we have
that working.
changelog_begin
changelog_end
* .
changelog_begin
changelog_end
* .
changelog_begin
changelog_end
* .
changelog_begin
changelog_end
* ledger-api-test-tool: Remove MonotonicRecordTimeIT.
This only makes sense for KV ledgers; they can implement it themselves
now.
CHANGELOG_BEGIN
- [Ledger API Test Tool] The optional ``MonotonicRecordTimeIT`` test
suite has been removed as it doesn't apply to most ledgers. If it is
necessary, ledger driver implementors are encouraged to write their
own and/or copy it from the last published version.
CHANGELOG_END
* ledger-api-test-tool-on-canton: Forget about MonotonicRecordTimeIT.
Navigator already had the possibility of autocompleting contract
identifiers, the only thing missing was to wire it in in full. This is
done mostly to inform how to address the more involved #12789.
changelog_begin
[Navigator] All input fields where a contract identifier can be passed
now provide the possibility of auto-completing based on the contracts
existing on the ledger.
changelog_end
As we transition to Canton, we use a new format of contract and party
identifiers that can break the UI of Navigator here and there. In
order to prevent this, we use the same rules as Canton does to shorten
identifiers (basically, elide any hash longer than 12 characters).
Full identifiers are still shown as part of the tooltip.
Furthermore, a tooltip suggests that clicking on the shortened
identifier copies it in full length on the clipboard (which is indeed
what happens). There are a couple of possible improvements to this
interaction, which cannot be handled as part of this PR due to time
constraint:
- the visual cue suggesting that the identifier can be copied can be
improved by adding a clipboard icon besides the label
- there is no visual feedback from copying the identifier, ideally the
user should somehow see that the copying took place (e.g. by turning the
clipboard icon suggested in the point above into a checkmark for a
couple of seconds)
changelog_begin
[Navigator] Contract and party identifiers are shortened on the UI
but can be copied in full by clicking on their label.
changelog_end