Encountering a PID lock in environment building
Environment build fails, showing
Path already locked by the same PID
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.
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:
- Automation Studio: v2.7.0
- 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:
- Running RCC command:
rcc config cleanup --downloads
- ..or by manually deleting the folder:
November 9, 2022