Domino 5.1.4 (July 2022)

Bug fixes

You can now run MongoDB update queries from Domino’s Admin application without restarting Domino. You might have to click Run several times to hit the primary replica. The primary replica is the only replica that can perform writes. In Domino 5.1 and higher, Domino’s Admin application could not perform update queries if you were working on a non-primary replica.

Resolved the performance issues with the endpoint used to list classic workspaces in the Workspaces dashboard (/v4/workspace/project/:projectId/ownerRunningClassicWorkspaces). You will no longer receive sporadic timeouts.

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

After deleting branches that were created in GitHub but not pulled (that is, they are not local on Domino), they are still shown in the Code menu in the Data tab of the workspace.

If you are comparing jobs that have large numbers of output files, you might encounter a 502 Bad Gateway error.

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.
- If you delete the file, it remains.
- If you move the file, the original and target file both exist.
- If you rename the file, the source and renamed file both exist.

If you rerun a successful job that accesses files from a dataset in a project owned by an organization, the job fails with file not found errors. Initial runs of the jobs succeed, but reruns fail with logging similar to the following:
```
2022-10-06 04:34:32 : FileNotFoundError: [Errno 2] No such file or directory: '/domino/datasets/local/reruns_fail/file.txt'
```
To work around this, start the execution as a new job.

If you use a forward slash (/) in a Git branch name, the forward slash and any preceding text is stripped. For example, if the branch was named test/branch1, it will be renamed branch1.
- In a workspace in a Git-based project, you can’t pull data because the branch doesn’t exist. You can push because this creates a new branch named branch1.
- In a Domino File System project that uses imported code repositories, you can push and pull directly to and from the branch (test/branch2) if you don’t change the branch in the menu. If you change the branch, you can’t return to the selection (test/branch2) because test/ is stripped. If you push to branch2, this creates a new branch named branch2.

The graph views are skewed incorrectly, in Domino’s model monitoring, when normalized values are small.
When exporting notebooks from JupyterLab workspaces, the system shows a 403 Forbidden Error with Blocking Cross Origin message.
When submitting a large number of jobs, Domino processes the first batch of jobs as usual but if the total number of jobs is larger than the execution quota for the user or the hardware tier, then the queued jobs are not promptly processed when capacity is available under the quota. This issue is resolved in Domino 5.2.2.

After you migrate from 4.x, scheduled jobs will fail until the users that own them log out and log in again. This issue is resolved in Domino 5.3.0.

Tip
You can also resolve this issue by removing all existing tokens in MongoDB, like this: db.user_session_values.remove({"key": "jwt"})

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.

Upgrading to this release from Domino 3.x or 4.x can cause Git credentials to be omitted from the dropdown when creating a new Git-based project. A workaround is available from Domino’s Customer Success team.

Model Monitoring data sources aren’t validated. If you enter an invalid bucket name and attempt to save, the entry will go through. However, you won’t be able to see metrics for that entry because the name points to an invalid bucket.

A limit overcommit error (OOMKilled) is occurring frequently on the prometheus-adapter pod in Domino’s Integrated Model Monitoring. The current workaround is to increase the limits. This issue is resolved in Domino 5.5.0.

If the Model Access Token Vault migration runs more than once, it wipes tokens from Mongo and Vault, and users need to regenerate their Model Access Tokens in the UI. This is fixed in Domino 5.4.0.

"Other" Git service provider URLs not ending in ".git" fail to work when you attempt to create a project from a Git repo or add a Git repo to a project. This issue is fixed in Domino 5.5.0.

Configuring prediction when setting up prediction capture for Model APIs causes predictions to not be captured. This issue is resolved in 5.4.0.

When restarting a Workspace through the Update Settings modal, External Data Volumes are not mounted in the new Workspace. Follow the steps to mount External Data Volumes. This issue is fixed in Domino 5.9.0.

Viewing dataset files in an Azure-based Domino cluster may lock files, preventing them from being deleted or modified. Restarting Nucleus frontend pods will release the lock. This issue is fixed in Domino 5.11.1.