About Domino
Domino Data LabKnowledge BaseData Science BlogTraining

Domino 4.5.2 (August 2021)

See also the fleetcommand-agent Release Notes.

Bug Fixes

  • Reduced excessive calls to fetch logs for failed jobs from the getLogsWithProblemSuggestions endpoint, which was causing some pods to run out of memory.

Known Issues

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

  • 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 upgrading from Domino 4.x to 5.1, contact Domino’s Customer Success team for access to the migration script that provides a workaround for this issue.

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

  • 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
    		 To avoid falling out of sync with the Git repository, always modify requirements.txt in the repository first and then copy it to your Project’s Artifacts folder.

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