Noves-Inc/canton-data-app released Canton Data App 4.2.7
github.com · Read at source ↗
# Canton Data App 4.2.7 ## Database timeouts and diagnostics - Helm exposes database pool size, connection timeout, and command timeout as individual values. The default maximum pool size is 40 and command timeout is 120 seconds. Connection acquisition keeps its 15-second default. Existing connection-string Secrets remain supported. - Automatic diagnostic reports identify the database
Canton Data App 4.2.7 was released on November 3, 2026, introducing configurable database timeouts, expanded diagnostics, background history repairs and changes to issuer reporting and data sharing.
Database configuration
Helm now provides separate settings for database pool size, connection timeout and command timeout. The default maximum pool size is 40, command execution has a 120-second timeout, and connection acquisition retains its 15-second default. Existing connection-string Secrets continue to work.
Command timeouts remain distinct from application request deadlines. Raising the command timeout does not lengthen every history request or eliminate database resource constraints.
An explicit `INDEX_DB_CONNECTION_STRING` overrides the individual settings. Installations using that override must either update the string or remove it, retaining any necessary TLS options. Docker Compose defaults are unchanged; details are available in the database configuration documentation.
Diagnostic evidence and recovery
Automatic diagnostic reports now identify the database operation, validator node, failure phase and configured timeouts, alongside available connection-pool and database-wait evidence.
That evidence is preserved both when a request reaches its deadline while awaiting a connection and when a fatal database error is sanitized for reporting. Reports separate the evidence available for:
- Acquiring connections.
- Executing commands.
- Reading results.
- Performing bulk writes.
For slow operations, reports may include bounded information about database waits and blocking sessions. The added evidence excludes SQL text, query parameters, returned rows and credentials, and remains governed by each installation’s diagnostic consent settings.
Diagnostic delivery also recovers automatically from temporary failures.
History repairs and participant access
Compatible corrections to pending-token-offer history now run in the background, allowing new activity to continue through history, dashboards, Flow and exports. A repair scope that fails stays visible without holding up unrelated repairs.
Participant token refreshes and authorization retries now have bounds. Traffic indexing remains inactive if capture is disabled, while permission failures halt repeated uptime refresh attempts.
Issuer reporting and data sharing
Issuer reports retain payment evidence and calculation settings, differentiate verified zero emissions from absent evidence, and prevent registry payments from being deducted twice.
Saved DA Utility reports open immediately, with refreshes occurring in the background. Summaries, round-level details and downloads now apply consistent emission evidence and historical fallback calculations.
Detailed issuer CSV exports retain the chosen validator and stream the download rather than buffering the full report in browser memory.
Fixed-size data-sharing proposals must have their saved file available. Once a proposal is accepted, that file is sent automatically.
Upgrade requirements
The release instructions call for the complete 4.2.7 Compose bundle or Helm chart, together with its pinned backend, frontend and database images. The frontend shows version 4.2.7.
The update introduces database metadata for background history repairs. Startup migrations retain existing history and leave the database compatibility level unchanged. Operators are instructed to back up the database before upgrading and let startup preparation complete, following the upgrade guide.
Image digests are recorded in the attached release manifest. The attached chart and manifest are covered by `SHA256SUMS`.
Release record and downloads
GitHub lists the release as the latest for `Noves-Inc/canton-data-app`. It was published by juanlenoves, with tag `v4.2.7` and commit `6bed994`.
The commit was created on GitHub.com and carries GitHub’s verified signature. Its verification is displayed as November 2, 2026, at 07:26 PM, using GPG key ID `B5690EEEBB952194`.
The release has five assets. The three attached files carry the timestamp 2026-11-03T00:27:18Z:
- `noves-canton-app-4.2.7.tgz` — 18.7 KB
SHA-256: `26a9e342d473b63f88abce900c9eab3d1974ba8da93f8e022190cb8c49ffac75`
- `release-manifest.json` — 1.25 KB
SHA-256: `ccaa55483bbdc6e2f535970e1e91ac978ee4847b16b45522705d516e3415936f`
- `SHA256SUMS` — 181 bytes
SHA-256: `c7bd30b5c03f7201a0b3b47892597f7b908bdbed045904ed625c32d43e4a77ed`
Source archives are also available in ZIP and tar.gz formats, both timestamped 2026-11-03T00:26:31Z.
Sources & attribution
- Published
- Nov 3, 2026 · 12:27 AM UTC
- Source
- github.com
- Publisher
- github.com
Full attribution under the Digital Millennium Copyright Act (DMCA), 17 U.S.C. § 512: this article is an original report by Canton Intelligence that summarizes the reporting of the publishers named above, links to their original work, and reproduces no protected expression beyond brief factual reference and in-line attribution (“according to github.com”). All rights in the underlying reporting remain with the publishers listed; nothing here implies endorsement by or affiliation with them. Rights holders may request correction, update or removal through the contact address published at infiniti.w3ai.io.