About Domino
Domino Data LabKnowledge BaseData Science BlogTraining

Domino 4.4.2 (May 2021)

See also the fleetcommand-agent Release Notes.

New Features

  • New External Data Volume types are now supported: Windows Share (SMB), and EFS.

  • Project cards now show executions on the footer, allowing you to see at a glance which projects have workspaces, running jobs, or apps.

Bug Fixes

  • Fixed an issue that caused an error in displaying projects after deleting a project that had an External Data Volume.

  • Fixed an issue that made the cursor appear in the wrong location when editing compute environments using Chrome browser on Windows.

  • Fixed an issue that caused snapshots not to be cleaned up and visible errors on long-lived workspaces.

Known Issues

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

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

  • As a system admin, when creating a project on behalf of another user, you will receive a 403 error.

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

  • 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.

  • 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.

    Note

  • 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.

  • 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.

    Tip