Robocorp Lab changelog and release notes

Robocorp Lab (4.11.3)

March 3, 2021

Fixes and Improvements

  • Code-completion is now a lot faster, supports continuous hinting and should work on all platforms

    You need to wait for the environment to be ready: RCC | Idle before LSP is enabled for RobotFramework

  • Robot templates updated to latest rpaframework v7.6.0
  • RCC v9.5.4 update brings in MicroMamba robustness improvements
  • Added cancellation for Run Robot
  • Lab kernel fixes in preparation for coming RobotFramework v4
  • Fix for macOS /tmp -folder permission problems in multi-user cases

Known issues

  • JupyterLab V3 has a new "Simple Interface Mode" that activates if you resize the editor window to a small enough size.
    • To get back to the standard interface, go to: View -> Deactivate Simple Interface.
    • We are looking into disabling this functionality because it appears to be rarely useful in automation cases.
  • On macOS Big Sur, the auto-update Restart Now closes and updates the Lab correctly but does not automatically restart the application.

Robocorp Lab (4.10.4)

February 11, 2021

Hotfix release

v4.10.3 highlighted that old environment caches had been corrupted by network outages etc., during environment setups. These environments were now causing failures when restarting the newer version.

If you hit an error on Lab start-up, you can restart Lab.
Robocorp Lab will clean-up old environments and try a fresh start.

Other Fixes

  • Robots using RPA.Desktop.Windows no longer cause environment cache actions
    • Library is generating files during execution that RCC detected for clean-up.
    • Runs for these robots are now faster, and the cache environments will work better with VsCode.
  • Fixed outputs for robots using pandas.
    • Dataframe outputs are now shown correctly in RobotFramework executions in Lab.
  • Fixes to LSP
    • Stability improvements on Windows.

Known issues

  • JupyterLab V3 has a new "Simple Interface Mode" that activates if you resize the editor window to a small enough size.
    • To get back to the standard interface, go to: View -> Deactivate Simple Interface.
    • We are looking into disabling this functionality because it appears to be rarely useful in automation cases.
  • On macOS Big Sur, the auto-update Restart Now closes and updates the Lab correctly but does not automatically restart the application.
  • LSP restarts are still having problems on Linux and macOS.

Robocorp Lab (4.10.3)

February 8, 2021

Updates

  • Support for old form package.yaml and entry point scripts dropped
    • See migration guide
    • The robots still open in Lab but Run Robot gives out an error.
    • Deprecated in 1.10.2020
  • Lab uses RCC v9 with new cleaned up templates.
  • Lab now uses conda-forge as the main source of packages.

Fixes and tweaks

  • Fixes for Lab startup errors
    • Seen as INIT_3_10 and INIT_4_10 errors in start-up
    • Environment cache corruption protection added
    • Environment setups support for Windows machines running non-Unicode codepages
    • ROBOCORP_HOME validation and fixing now in Lab's pre-checks UI
  • Security updates to Electron
  • Image-based locators no longer store the origin image for privacy protection.
  • Lab quitting and restarting fixes on Mac
    • Application exit and restarts now work as intended on Mac
    • CMD+Q now quits

Known issues

  • JupyterLab V3 has a new "Simple Interface Mode" that activates automatically if you resize the editor window to a small enough size.
    • To get back to the normal interface go to: View -> Deactivate Simple Interface.
    • We are looking into ways of disabling this functionality because it appears to be rarely useful in automation cases.
  • On macOS Big Sur the auto-update Restart Now closes and updates the Lab correctly but does not automatically restart the application.

Robocorp Lab (4.9.11)

January 21, 2021

Updates, fixes and tweaks

  • Updated to the official version of JupyterLab v3.
  • Lab now uses MicroMamba instead of MiniConda to build the environments, resulting in a considerable speed boost during builds.
  • Lab now supports using the ROBOCORP_HOME environment variable to change the location of common data for all Robocorp Applications.

The mysterious case of 'spaces in username'

NOTE: This only affects users with operating system usernames containing spaces or special characters (like scandics).

The solution is for now to use the ROBOCORP_HOME environment variable to point to a 'tool friendly' -location on the system (For example: C:\temp\robocorp).

The next Lab release will include a more user-friendly way of managing this setting.

Background & next steps:

During MicroMamba tests, we noticed that having spaces in username (and special characters like scandics) does not affect only users on Windows, but also on other operating systems in addition to internal tools like pip.

While testing for the shift to MicroMamba, we realized that the issues caused by spaces or other special characters in the username affect users on all operating systems (not only on Windows), in addition to interfering with the correct functioning of tools like pip.

So we had to change direction from just solving the issue for Lab on Windows to solving it for all users on all platforms.

The fix is included in version 8 of the underlying tool RCC: this means that the Vs Code extension will also benefit from it at the same time.

RCC executions will now warn you in case it detects issues with your ROBOCORP_HOME location.

Once we have the user-friendly implementations for fixing the issue in the tools we will change RCC to just block execution in these cases.

Known issues

  • JupyterLab V3 has a new "Simple Interface Mode" that activates automatically if you resize the editor window to a small enough size.
    • To get back to the normal interface mode go to: View -> Click on Simple Interface to deactivate.
    • We are looking into ways of disabling this functionality, because it appears to be rarely useful in automation cases.
  • Some reports for errors INIT_3_10 and INIT_4_10 under investigation
    • These errors seem to be really specific to individual system setups, so please submit issues on these with your email attached so that we can get in contact with you and figure out the root causes.
    • Some cases have been tied to firewalls blocking outbound traffic. To solve these kind of issues, you can now find details on how to configure your firewall in the troubleshooting section.

Robocorp Lab (4.8.8)

December 22, 2020

Fixes and tweaks

  • Fix for the Restart and Run All Cells -functionality (Upgraded to JupyterLab v3 release candidate 14)
  • Fixed the "stuck when opening a robot" bug.
  • Improved code-completion (Minor tweaks in the LSP functionality)

Known issues

  • JupyterLab V3 has a new Single-document mode that activates automatically if you resize the editor window to a small enough size.
    • To get back to normal mode go to: View -> Click on Single-Document Mode to deactivate it.
    • We are looking into ways of disabling this as it really serves little purpose in automation cases.
  • Some reports for errors INIT_3_10 and INIT_4_10 under investigation
    • These seem to be really specific to the system setup so please submit issues on these with your email attached so that we can get in contact and figure out the root causes.
    • Some cases look like antivirus software is causing file locks. We are using VirusTotal to scan our software deliveries but individual antivirus setups are notoriously hard to pinpoint.