Encountering a PID lock in environment building

Symptoms

Environment build fails, showing Path already locked by the same PID

Reason

The problem is caused by issue #1915 in micromamba. The problem only affects Windows and happens only when a process is forcefully killed during micromamba caching.

Solution

The issue is fixed in micromamba v0.27.0, which is included in RCC v11.28.0 and newer.

This version of RCC is used in our tools starting from versions:

• Assistant: v1.8.3
• Workforce Agent: v1.2.54 / v6.20.9
• Robocorp Code extension for VS Code: v0.39.0

You can also resolve the issue by:

Note: Since RCC v20.1.1, Sema4.ai is the default product strategy. Add the --robocorp flag to all RCC commands when working with Robocorp tooling.

• Running RCC command: rcc --robocorp config cleanup --downloads
• ..or by manually deleting the folder: %localappdata%\robocorp\pkgs