Domino 4.5.1 (July 2021)

Fixed an issue that made the EDV not mounting when runs are initiated via the API or via the Save and Run button in the Files tab

Fixed collecting all metrics from nucleus by the prometheus server

Reduced cardinality to help with Metrics Explosion

Addressed build failures for DAD related environments that started on 07/04/21 due to an external service dependency going away

Fixed an issue that prevented creating new workspaces in a project where tag was removed from the Snapshot

In R Studio workspaces, the default home directory is not set to /mnt/code for Git-based projects and /mnt for Domino File System (DFS) projects.

When loading the Administrator page that shows datasets and snapshots, sometimes the load time is long which causes timeouts.

Stopping a workspace on a heavily-loaded Domino sometimes results in a 502 error code shown in the notebook iframe of the workspace session view.

A metrics explosion is causing the nucleus Prometheus endpoint to take a long time to service requests so not all metrics from nucleus are being collected by the Prometheus server.

An external dependency was removed on 7/24/21, causing build failures for DAD-related environments.

When upgrading from Domino 4.x to 5.1, Domino does not correctly handle environment revisions that have both a Docker image and a base environment revision. This issue is resolved in Domino 5.2.0.

When an API key explicitly passed as an api_key argument and the DOMINO_TOKEN_FILE environment variable is set, Domino uses the token authentication. This issue is resolved in Domino 5.2.0.

When Flask apps generate links, this can result in unwanted 302 redirect behavior. This issue is fixed in Domino 5.2.0.

When a Model API fails while retrieving files from git using SSH keys, the private key and the key password, if any, may be exposed in the Domino log. This issue is resolved in Domino 5.2.0.

The Import Project drop-down does not display projects owned by organizations of which you are a member. This issue is resolved in Domino 5.2.0.

In a Git-based project, requirements.txt must be in your project’s Artifacts folder in order to be picked up by an execution, instead of at the root level in your project files.