unamemight work on Unix (not Win though)
The self-hosted runner: cirun-robostack--ros-humble-bedf657 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
I have no idea how to patch qt-gui-cpp for Windows though - if someone has some capacity to setup a local build of ros-humble on Windows this would be awesome (let me know and I can provide more details)
Unfortunatly this week I am quite constrained and next week I will leave for vacations, so I guess I can do it around ~20 of August
linux64Humble env? I'm looking to install MoveIt Setup Assistant and getting
mamba install ros-humble-moveit-setup-assistant --dry-run Encountered problems while solving: - package ros-humble-moveit-setup-assistant-2.5.3-py39h7ac24ad_1 requires qt-main >=5.15.4,<5.16.0a0, but none of the providers can be installed
moveit_setup_assistant is assuming Python 3.10+ dataclasses (in
moveit_configs_utils) with a
slots kwarg in the
(humble-msa) dan@schelkunoff:~$ ros2 launch moveit_setup_assistant setup_assistant.launch.py debug:=true [INFO] [launch]: All log files can be found below /home/dan/.ros/log/2022-08-03-18-34-30-806882-schelkunoff-77251 [INFO] [launch]: Default logging verbosity is set to INFO [ERROR] [launch]: Caught exception in launch (see debug for traceback): Caught exception when trying to load file of format [py]: dataclass() got an unexpected keyword argument 'slots'
/path/to/mambaforge/mambaforge/envs/humble-msa/lib/python3.9/site-packages/moveit_configs_utils/moveit_configs_builder.py Line 84:
@dataclass(slots=True) class MoveItConfigs: """Class containing MoveIt related parameters.""" # A pathlib Path to the moveit config package package_path: Optional[str] = None # A dictionary that has the contents of the URDF file. robot_description: Dict = field(default_factory=dict) ... etc.
There's probably something more subtle that could happen for a patch beyond just disabling the slots ... will report back if that works. It looks like manually declaring
__slots__ conflicts with setting the default values.