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
* 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
* Add support for aggregated transaction metering
changelog_begin
Support added for aggregated transaction metering
changelog_end
* Update with review comments
This reverts a small part of 9e1e42d27c
(#12901).
Microsoft seems to have given us our free parallel jobs back, so we can
run the patch_bazel job again.
Fixes#12900.
CHANGELOG_BEGIN
CHANGELOG_END
This should hopefully get CI working again.
There are two changes in here:
1. We can no longer change our patched Bazel. I didn’t switch away
from the current patched version for now (we upload it to gcp bucket
so it still works fine even if we cannot build it) but if we upgrade,
we need to go to an unpatched version for now.
2. We need to get `az` from dev-env. I tested the self service compat
job stuff and it works fine with this but there is a chance other
parts don’t.
changelog_begin
changelog_end
Undoing an unnecessary refactoring from #12187
stefanobaghino-da confirmed this fixes the memory leak he observed
in "long" running navigator sessions.
CHANGELOG_BEGIN
CHANGELOG_END
* Removed no-action TODOs
changelog_begin
changelog_end
* Assert self-service error codes in SequenceSpec
* Move InternallyInconsistentKeys and InternallyDuplicateKeys to LedgerApiErrors.WriteServiceRejections
* Restructured ledger bridge metrics
* Buffers before each processing stage
* Do not log the failure stacktrace on ledgerId lookup
* Addressed review comments
* Buffer size before prepare submission is 128
* Support getting started guide on Daml Hub
This is annoyingly complex so let me try to provide an explanation for
the changes:
1. On Daml hub, we need to use a separate token for the public party
and the user party.
2. This means that we need separate contexts. I cannot get access to
the default context (not exposed) so annoyingly even for the user context we need to
use a custom context
3. The way to get access to the public party in Daml hub is via a
hook that reads it from the context. However, we cannot call that
within the login callback so the way things work now that we login
immediately show a "Logging in..." loading screen while we run the
background query. This is actually kinda nice since it means
something happens immediately after clicking login.
I’m sure there are better ways of handling this, my react foo is very
weak but this is what I managed to get to work.
Tested locally as well as on Daml hub and both work fine.
changelog_begin
changelog_end
.
.
.
.
.
.
.
* s/any/void/
* fmt
