Domino 4.6.0 (August 2021)

Kubernetes 1.18–1.20

Dask on Domino - Domino introduces the ability to dynamically provision and orchestrate a Dask cluster directly on the infrastructure backing the Domino instance. To learn more, see Dask on Domino.

Branch selection in Git repository file browser - Git-based project users can now select from any branch and the latest 10 commits using drop-down lists, then browse the directories of linked Git repositories natively from the Code section on the project page. To learn more, see the documentation on Git-based projects.

GitLab integration - GitLab users can now create a new GitLab repository during the Git-based project creation process. To learn more, see the updated steps 8-9 in the documentation To create a Git-based project.

Domino Standard Environment - The Domino Analytics Distribution has been replaced by the Domino Standard Environment. The new DSE approach provides multiple base images for different use cases. The default DSE is published on Quay. You can find the full collection of Domino published environments in the Compute Environment Catalog. Existing environments do not get updated to use the new DSE on upgrade. See Domino Standard Environments.

Co-installation with the core Domino platform - Deploy an instance of the Model Monitor in a cloud (AWS, Azure, GCP) or on-premises environment alongside the core Domino platform. Single sign-on enables seamless authentication and access to both platforms. To enable the Model Monitor at install time, see the new Domino configuration settings.

Enterprise-scale model monitoring - Compute data drift and model quality metrics at enterprise scale for hundreds of models with hundreds of features and billions of predictions.

Comprehensive model quality metrics - Get comprehensive model quality coverage with varied reporting and metrics, including accuracy, precision, recall, F1, AUC ROC, Log Loss, Gini norm, confusion matrix, and per-output-class breakdowns.

Integration with High-capacity Data Storage - Ingest data from Amazon S3 and Hadoop Compatible File Systems (HCFS) that include Azure Blob Store, Azure Data Lake (Gen1 and Gen2), Google Cloud Storage, and HDFS to enable model monitoring.

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

Improved handling of the case when a project owner without the Practitioner role attempts to publish an app. Whereas previously this could leave the app stuck in a “Never Started” state, now the attempt will be cleanly denied.

Updated guidelines for installing python-domino library in the egg format.

Allow execution of .ipynb files that have spaces in the filename.

Fixed an issue with the Model API generating exceptions when the model is hosted outside Domino. Model API applications deployed via Export to External Registry will now run cleanly.

Fixed caching issues that caused deleted folders to reappear in subsequent runs, and folders from cloned git repositories to reappear after the action to stop and discard changes.

Aligned the progress output for a pending Domino Workspace to report the progress as ‘Pulling' until all necessary images are pulled, instead of prematurely displaying ‘Running'.

Fixed a synchronization issue in starting Runs (such as scheduled jobs) which was causing a small percentage of runs to error out with a message in the execution log “Failed to create pod sandbox”.

Fixed CLI BigSur MacOS issue with deleted files synchronization.

Improved performance of Models to handle multiple simultaneous queries without long queueing times.

Fixed caching issues that caused deleted folders to reappear in subsequent runs.

Enhanced error messaging in case of environment build failure due to Dockerfile parsing errors.

Fixed JWT credential propagation for Domino installations on OpenShift.

Improved the Admin usage page to handle a large number of runs in the system without becoming unresponsive or displaying an error message.

Fixed an issue where, on a heavily-loaded Domino, stopping a workspace sometimes resulted in a 502 error code shown in the notebook iframe of the workspace session view.

For executions with clusters, improved reporting of the cluster hardware tier in the execution details (Job details, workspace details) to consistently show the hardware tier name rather than the ID.

Improved the workspaces view to show all workspaces after the user stops any given workspace, rather than showing only the stopped workspace.

Optimized loading of the Administrator page that shows datasets and snapshots, to cut down on the page loading time and prevent potential timeouts.

Fixed a shared dataset listing issue where multiple datasets with the same project name were not being displayed.

Improved handling of invalid credentials during creation of a Git-based project to notify the user of the problem.

Optimized loading of the Administrator page that shows datasets and snapshots, to reduce the page load time and prevent potential timeouts.

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.

If client.distributed.performance_report is invoked more than once in a Jupyter notebook, then Dask performance reports may fail as described here: https://github.com/dask/distributed/issues/3858

When running a workspace on the Domino Standard Environment (DSE), performance degradation on bigger workloads can occur. Scripts may take longer to complete. In this case, the Domino Minimal Environment (DME) is recommended instead of the DSE.

After upgrading Kubernetes, X509 certificate signed by unknown authority errors appear and Domino fails to deploy workspaces, jobs, apps, models, and so on.

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

If you create a subfolder in a dataset, and then navigate into the subfolder and click Take Snapshot > Include all files, the snapshot status hangs.

If you try to access a shared datasets that you don’t have access to, you receive a 403 error.

When a dataset has more than one subfolder, if you initiate a snapshot from a folder other than the root of the dataset, the snapshot is incomplete.

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.

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.

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.

The Kolmogorov–Smirnov Test, Wasserstein distance, and Energy Distance tests can lead to unpredictable results. Do not use these tests.

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.