Robocorp Lab (4.20.18)
- Update to RCC v11.1.3
- Reduces the number of parallel workers to reduce the file I/O load that seems to affect some Windows machines.
- Now using
Copy and renamepattern to block any termination in the middle of file writing from causing broken files.
- Should fix the INIT_3_10 and INIT_4_10 errors that some users have been hitting hard.
- v11 is now cleared from all old-style cache commands and logic
rcc env ...-commands removed and replaces by either
rcc holotree ...or
rcc config ...commands
- Breaking command changes highlighted in RCC changelog
- Lab startup checks improved > removed redundant initial checks
- Having `defaults '-channel in conda.yaml will cause errors; now is the time to get rid of that.
- Parts of the Lab basement are no longer shipped via defaults -channel, causing weird errors.
- Templates and robots in Robocorp Portal have been updated since February, but basically, you only need to remove that one line.
channels: - conda-forge dependencies: - python=3.7.5 - pip=20.1 - pip: - rpaframework==11.4.0
- "Lab is unresponsive" on some machines.
- While we still have not been able to repro this on our side, we got some profiler data that helped us get further, thanks to some accommodating community members.
- Patch v4.20.18 now avoids most of the failure cases we have seen in a way that breaks the failure cycles and resumes better.
- Patch v4.20.18 also reduces the number of parallel file actions, which seems to be the triggering aspect.
- Big dependencies still take time, and at the moment, pip for example does not support any parallel actions, so machine utilization is really low during pip steps.
- We have a couple more ideas in the works still on this matter.
September 23, 2021