Code Browser

Logs for request timeouts don't seem to properly take customTimouts into account

dpm release should be triggered by `VERSION` file change rather than git tag

revert damlc docs back to latest stable when cutting 2.3

Test that setting pv=dev works

Add package names to error messages / payloads involving package IDs

Use Splice.Amulet.CryptoHash functions directly once there available via rebase or merge

Add a test that compares reward computations to detect if Scala and Daml diverge.

Ensure totalAppRewardAmount never exceeds total issuance

Add advisory lock to SqlIndexInitializationTrigger

Disable possibility of vote on the same field when another proposal is in progress

Test and adopt new default value for `DefaultSetBalanceRequestSubmissionWindowSize`

Make sbt fail again on all damlc warnings

Polish release notes for token standard v2

Test v1 history parsing for v2 allocation and transfer workflow

Support roll-forward LSU DR

ability to disable the transaction visualisation page in the wallet gateway

Switch to explicit serializability annotations in new V2 packages

parallelism parameter in config for parTraverseLimits

Enforce max lock duration for Amulet allocation and transfer instructions

Upload splice-util-token-standard-wallet by default on all validator nodes

Proposal: CIP-0105 Compliance Computation Module

[2.10.4-22] Update docs.daml.com

support uint256 natively in Daml

[2.10.4-21] Check that the release notes load in the IDE

[2.10.4-11] Create SDK release

[2.10.4-10] Ensure that Canton Code drop is up to date

[2.10.4-05] Prepare SDK Release Notes

Refactor: Do single call to retrieve the verdict with activity records

Consistent logging (using logger) in migrations

Enable check_canton_consistency for non-contributors (low prio cause unlikely non-contributors will not update canton)