Robocorp Lab (4.5.7)

A stabilizing release

So far, we have been focusing on implementing the key features in Lab. This release is focused on stability improvements.

The long filenames limit in Windows can cause issues with Robocorp Lab. Allowing long filenames should fix these issues. Robocorp Lab now checks if the long filename support is enabled.

The Help menu on the welcome screen now allows for submitting issue reports. Sending an issue report delivers the needed logs and details securely.

Another stability item on the horizon is the JupyterLab V3 update. This should reduce startup errors and improve performance.

Fixes

  • macOS "Big Sur": Fixed a bug in UI locator snipping.
  • Fixes to temp folders and file locking in Windows should reduce INIT errors or Lab not opening. chromedriver can still lock files on Windows but should not prevent Lab usage.

Known issues

  • Opening a robot with a conda.yaml that is not found in the cache takes a minute or two (conda package loading), and the Lab is missing the UI notification for this.
    • Closing the Lab view does not stop the cache set up, so the user needs to wait for it to complete.
    • Environment build status notification coming to the next release.
  • JupyterLab v2 builds extensions on target machines, making Lab initialization error-prone. The upcoming JupyterLab v3 update should reduce startup issues.
  • Execution does not always start when using Restart Kernel and Run All Cells... (all cells display [*]).
    • Cell-by-cell and Robot Run can be used as a workaround.
    • Running Restart Kernel and Run All Cells separately can be used as a workaround.
    • Affects macOS "Big Sur", but also some Windows installations.
November 24, 2020