Domino 4.6.2 (November 2021)

This release includes significant performance and stability improvements in many components throughout the Domino platform.

The execution engine is now scalable to handle thousands of running executions.

The Projects API (/v4/projects) no longer times out on deployments containing a large amount of historical data.

Jira integrations now authenticate correctly during setup.

Environments detail pages now load more quickly.

In launch dialogs for workspaces, model APIs, jobs, and so on, the Launch button now loads quickly.

Workspaces become unstoppable and their statuses don’t change when the timestamps on the run’s status changes array are incorrect.

In the Control Center’s navigation pane, click Assets. Domino displays a "Failed to get assets" message and takes a long time to load the assets.

You cannot delete, rename, or move a .gitignore file in a Domino File System project.

Any installations that require a third-party, non-Quay.io registry, and manage Istio with Domino, will fail to install or upgrade with Domino 4.6.0-4.6.2. Contact Domino for assistance working around this issue.

When directory names are empty (“”) or contain the slash (/) character, execution failures and a dispatcher crash occur.

Project collaborators with Launcher User or Results Consumer permissions can access the project’s files.

When you create a new dataset and add a folder with a numeric folder name, the snapshot creation is stuck in Pending unless manually cancelled.

A customer is unable to integrate to Jira due to authentication issues.

Environment detail pages loading slowly and timeout if they have < 50 revisions and many linked projects.

In Launch dialogs for workspaces, model APIs, jobs, and so on, the Launch button can take 15-20 seconds to activate.

Database migrations even after one pod’s migration fails, and the error may be difficult to locate in the migration log. This issue is resolved in Domino 5.2.0.

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.

Sync operations for deployments backed by SMB file stores can sometimes result in unintended file deletions. This issue is fixed in Domino 5.2.0.

You cannot delete a .gitignore file in a Domino File System (DFS)-based project. This issue is fixed in Domino 5.2.0.

Apps may fail with unusual error messages. This issue is resolved in Domino 5.2.0.

Opening an un-cached workspace can cause the workspace to get stuck in the "Pulling" status. This is fixed in Domino 4.6.4.

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.

When starting a workspace, the application sometimes gets stuck in the Pulling status, even though the logs indicate that the workspace started successfully. If this occurs, stop and start the workspace again. This issue is fixed 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.

Domino can become inaccessible after a fixed uptime period when running on Kubernetes 1.21 or higher. See this knowledge base article for the workaround. This issue is fixed in Domino 5.3.1.