Domino 4.4 (February 2021)

Durable Workspaces – Stop and resume your workspaces sessions as needed. Your work persists from session to session, ensuring that you never lose your work and enabling you to commit your work to version control whenever you want. To learn more, see workspace sessions.

Git-based Projects with CodeSync – Native integration with widely used Git repositories is provided by CodeSync technology in new Git-based project type to help data scientists save, find and reproduce work, and engage in version-controlled, code-based collaboration with other team members. Create branches, commit your code, and push or pull changes to your code, all from within a workspace, in a Git-based project with CodeSync. To learn more, see Git-based Projects with CodeSync.

The Domino Analytics Distribution (DAD) has been upgraded to use Python 3.8. Notable upgrades are listed below. See the corresponding changes outlined in the "Breaking Changes" section.

The default Domino Analytics Distribution (DAD) uses Python 3.8, however, PySpark 2 does not support Python 3.8 or higher. If you need a PySpark 2 environment, make sure to build it from images that use Python versions < 3.8.

CUDA has been removed from the upgraded DAD in Domino 4.4.0 to keep the size of the DAD image to a minimal size. If you need to use CUDA 10 or CUDA 11, use the following image: quay.io/domino/base:Ubuntu18_DAD_Py3.8_R4.0-20210127_CUDA11.0_full. Drivers must be present on the underlying hosts.

You can now set your own volume size for your workspace sessions and Jobs. Your Domino administrator can configure the minimum, maximum, and default sizes for the volume. In Domino 4.4.0, the default volume size is 10 GB. If your Domino deployment previously utilized a custom volume setting in a prior version of Domino, make sure to edit the corresponding central configuration values after upgrading to Domino 4.4.0 to ensure your runs execute as intended.

If you are upgrading to 4.4.0 from Domino version 4.1.9 or earlier, the following Keycloak client mapper must be manually created prior to upgrading if you are using roles synchronization. See central configuration for more information about the Central Configuration flag for Role synchronization.

If you are using group synchronization, you must create the domino-groups-mapper. See SSO group and role synchronization for details.

URL authorization will fail when attempting to use an older version of the Domino CLI with Domino 4.4.0. To avoid this issue, we recommend reinstalling the Domino CLI.

After modifying email settings, manually restart services for the email settings to take effect.

Emails are not sending to user(s) mentioned using the "@" tagging feature in a file comment or job comment. Communicate with the intended user(s) in a different way.

If you’re launching a Job in a Git-based project with CodeSync, use absolute paths if you’re specifying the name of a file outside of the /mnt/code working directory. The .. command is currently not supported.

If you’re using a Launcher in a Git-based project with CodeSync, note that files or scripts specified in the “Command to run” text area will execute in /mnt/code. Be sure to account for this if your script results in outputs you’d like to persist.

Fixed an issue that prevented workspaces from launching in Domino if Domino was deployed with Istio.

Fixed an issue that affected file creation and file editing in projects.

Fixed an issue that prevented Spark clusters from launching if they used a GPU-based hardware tier.

Fixed an issue that prevented users with the "Practitioner" role from creating a project.

Fixed an issue that prevented Domino runs from executing properly if a file in a linked repository contained non-ASCII characters.

Restored the "Support" button for all Domino 4.x deployments.

Fixed an issue that prevented Domino workspaces from being stopped.

Fixed an issue that prevented data frames from being read properly when using a Spark cluster.

Fixed an issue that prevented model APIs from being properly exported.

Fixed an issue that caused failed attempts to push to a protected branch in an external Git repository to appear to have succeeded.

Fixed an issue that prevented a Git credential from being created if the domain was entered as an IP address.

Fixed an issue that prevented new models from being created.

Fixed an issue that prevented project settings from being properly propagated to Spark clusters.

Fixed an issue that allowed users to edit their own roles.

Fixed issues that prevented usage report emails from being sent.

Fixed an issue that prevented datasets from mounting properly when executing a Domino run using the "Save & Run" option present in the "Files" page of a Domino project.

Fixed an issue that prevented SMPT configuration values from being properly set.

Fixed an issue that prevented users from viewing datasets in their project if the dataset originated from an imported project.

Fixed an issue that prevented scratch spaces from being assigned to workspaces that were launched from the "Files" page of a Domino project.

Fixed an issue that prevented workspaces from launching if a snapshot that was marked for deletion was mounted to another project through a shared dataset.

Fixed an issue that caused a 502 error when attempting to generate a user activity report.

Fixed an issue that prevented some Python-based extensions from functioning properly in workspaces that utilized VS Code.

Fixed an issue that caused files specified in .modelignore to continue to appear with a published model’s files.

Fixed an issue that allowed multiple hardware tiers to be designated as the "default" hardware tier for a Domino deployment.

Fixed an issue that affected the "Name" field in cloned hardware tiers.

Fixed an issue affecting “Command to Run” parameters when using a Launcher.

Chrome 88 on Windows 7

Firefox 85 on Windows 7

Safari 14 on MacOS 10.15 Catalina

Edge Chromium 88 on Windows 10

If an imported project or Git repository is added between workspace restarts, the system creates empty directories.

A pending Domino Workspace prematurely reports the progress as Running and is stuck there for a long time before it is actually running.

Models have long queueing times when handling multiple simultaneous queries.

The workspaces view shows only the stopped workspace, rather than all workspaces.

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.

Domino CLI on BigSur MacOS has issues with deleted files synchronization.

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

Every Domino execution causes the Domino CLI to print log4j errors, although this does not stop the CLI from working.

Model API Settings pages is crashing when there are empty environment variables in models.

If a 0-byte file exists, the Domino CLI does not upload the Dataset or Dataset Snapshot.

Control Center times out when loading large volumes of historical run data into the application.

The count of users with the Lite User role is not included in the Total Active Users statistics on the Users Admin page.

When launching RStudio 1.4, a Network Error occurs.

Customers requested the Intercom button be disabled because of the Support button. Domino is working with customers to determine how to make the Intercom button less invasive.

When importing projects, the user has access to files if exporting is disabled if this setting was initially enabled and then later disabled.

When a project owner is an organization, you cannot change the Workspace and Jobs volume size.

Sometimes after launching a workspace and logging in again, two workspaces start rather than one.

When auto shutdown is enabled for a workspace and you are working in a Git-based project with CodeSync, if the auto shutdown is triggered, the changes to mnt/code' are committed to Git but changes to`mnt/artifacts` are not synced/pushed.

Email notifications are not sent when using "@" to mention team members in a file or job comment.

When using the Domino Minimal Distribution (DMD), it fails to install some dependencies.

When deleting a project that had an External Data Volume, users receive a "Failed to get Projects" error message.

When using a Spark cluster, the data frame cannot be read properly.

When editing a Launcher’s settings, if you click in the text box next to Command to Run, typing a character eliminates previously created parameters.

Archived Workspaces and Jobs are not listed in the Workspaces page even though the Show Archived checkbox is selected.

Anonymous cannot run Launchers associated with public Domino projects.

When you stop a workspace, you can click a button to return to Domino. If you click that button, a new tab opens the Workspace page but another tab opens with a new Workspace too.

If you enter an invalid URI in the Import Git Repository dialog, the system hangs.

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.

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.

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.