* Upgrade sphinx
Don’t want to be stuck on 1.8.3 forever. The current version is
4.4.0 (this upgrades to 4.3.1 which is the latest in nixpkgs).
I did had to drop footnotebackref. This runs into the same issue as
https://tex.stackexchange.com/questions/137594/hyperref-footnotebackref-in-longtable
but just copying the fix doesn’t work and I don’t understand enough
about the details here to fix this myself.
We have 7 footnotes in the Daml docs + some in the Canton docs. That
does not seem worth sticking on a sphinx version from 2018 for just to
get backreferences from footnotes to the link on the same page.
changelog_begin
changelog_end
* turns out you need fonts maybe
* .
changelog_begin
changelog_end
* suppport :force: in daml-docs
changelog_begin
changelog_end
* speedy: short circuit precondition checking
Instead of evaluating all preconditions of templates and interfaces we
evaluate preconditions one by one and throw an exception as soon as we
find a failing one.
This implemented via a lazy SBCheckPrecond builtin and a foldleft
expression over the list of preconditions.
CHANGELOG_BEGIN
CHANGELOG_END
* Update daml-lf/interpreter/src/main/scala/com/digitalasset/daml/lf/speedy/Compiler.scala
Co-authored-by: Remy <remy.haemmerle@daml.com>
* Update daml-lf/interpreter/src/main/scala/com/digitalasset/daml/lf/speedy/SBuiltin.scala
Co-authored-by: Remy <remy.haemmerle@daml.com>
* fix SUnit -> Unit
* tests
Co-authored-by: Remy <remy.haemmerle@daml.com>
* wrap interfaces in SAny in speedy
* expect SAny representation for interfaces in builtins
* Update SBResolveVirtual
* SBResolveSBUInsertFetchNode uses SAnyInterface
* SBResolveSBUBeginExercise uses SAnyInterface
* Wrap 'this' in SAnyInterface for interface preconditions
changelog_begin
changelog_end
Part of #12792, this is the builtin we need to be able to effectively
store a TemplateTypeRep inside a template (i.e. you store a string
containing the template id, not a typerep).
changelog_begin
changelog_end
* sandbox-classic: Fix the class loader when retrieving the banner.
If the classloader is not explicitly provided to `Source.fromResource`,
it will use the current thread's class loader, which may not have access
to _banner.txt_. To avoid issues, we need to use the correct class
loader.
CHANGELOG_BEGIN
CHANGELOG_END
* sandbox-common: Get rid of a null check that should never fail.
Fixes#12881 by making the oauth2 test server invent user tokens
instead of claim tokens if you ask it to. As with the claim
tokens, these aren't "real" tokens backed by a participant
server, so only a subset of the tests makes sense, and we
abstract over the shared compatible tests accordingly.
CHANGELOG_BEGIN
CHANGELOG_END
* leave trigger service port for already-submitted issue #12831
* spin off another test idea, #12989
* Squash functionality ReadOnlyLedger hierarchy implementation into BaseLedger
changelog_begin
changelog_end
* Renamed BaseLedger to ReadOnlyLedgerImpl
* Removed BaseLedgerSpec test as it is redundant
* Package shifts
* Moves ReadOnlyLedger to package `index`
* Moves TransactionConversions and EventFilter to `appendonlydao.events`
* Refactorings:
* Extracted LedgerEndPoller out of ReadOnlyLedger
* Moves DispatcherLagMeter in its own file
* ReadOnlyLedgerOwnerBuilder
* Replace CacheIndex with MutableCacheLedgerEnd
* Rename DispatcherLagMeter to InstrumentedSignalNewLedgerHead
@S11001001 is taking care of testing today's release, so they get pushed back to the end of the line.
Please do not merge this before the release is fully tested.
CHANGELOG_BEGIN
CHANGELOG_END
Co-authored-by: Azure Pipelines Daml Build <support@digitalasset.com>
Specifically for the Java codegen, builds on top of #12977.
Makes sure we don't rely on PackageName.fromString and PackageVersion.fromString
to blow up when passed an empty string.
changelog_begin
changelog_end
* Fix parsing of java codegen module prefixes
I admit I have no idea what I thought when I wrote that split but it
was clearly nothing sensible.
changelog_begin
- [Java Codegen] Fix parsing of `module-prefixes` to support package
names containing dashes.
changelog_end
* reveiw comments
* Inline nameVersion
changelog_begin
changelog_end
* .
changelog_begin
changelog_end
* 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
