GUI Crash when resetting the simulation

When I reset the simulation the GUI crashes as per the video below:
https://github.com/user-attachments/assets/e09f64cb-f557-4253-9afe-f5f1934671e4
It follows the log after the reset is invoked:

[INFO] gz-sim-yarp-clock-system plugin Reset invoked.
[WARNING] No initial configuration found, initializing trajectory generator with current values
[WARNING] No initial configuration found, initializing trajectory generator with current values
[WARNING] No initial configuration found, initializing trajectory generator with current values
[WARNING] No initial configuration found, initializing trajectory generator with current values
[INFO] Initial configuration found, initializing trajectory generator with it
[INFO] Initial configuration found, initializing trajectory generator with it
[INFO] interrupt1 phase starting...
[INFO] interrupt1 phase finished.
[INFO] shutdown phase starting...
[INFO] Entering action level 5 of phase shutdown
[INFO] Executing detach action, level 5 on device lidarWrapY with parameters []
[INFO] All actions for action level 5 of shutdown phase started. Waiting for unfinished actions.
[INFO] All actions for action level 5 of shutdown phase finished.
[INFO] Entering action level 15 of phase shutdown
[INFO] Executing detach action, level 15 on device left_arm-mc_nws_yarp with parameters []
[INFO] Executing detach action, level 15 on device right_arm-mc_nws_yarp with parameters []
[INFO] Executing detach action, level 15 on device left_leg-mc_nws_yarp with parameters []
[INFO] Executing detach action, level 15 on device right_leg-mc_nws_yarp with parameters []
[INFO] Executing detach action, level 15 on device head-mc_nws_yarp with parameters []
[INFO] Executing detach action, level 15 on device torso-mc_nws_yarp with parameters []
[INFO] Executing detach action, level 15 on device left_leg-FT_wrapper with parameters []
[DEBUG] |yarp.device.multipleanalogsensorsserver| Detach complete
[INFO] Executing detach action, level 15 on device right_leg-FT_wrapper with parameters []
[DEBUG] |yarp.device.multipleanalogsensorsserver| Detach complete
[INFO] Executing detach action, level 15 on device left_arm-FT_wrapper with parameters []
[DEBUG] |yarp.device.multipleanalogsensorsserver| Detach complete
[INFO] Executing detach action, level 15 on device right_arm-FT_wrapper with parameters []
[DEBUG] |yarp.device.multipleanalogsensorsserver| Detach complete
[INFO] Executing detach action, level 15 on device head-inertials_wrapper with parameters []
[DEBUG] |yarp.device.multipleanalogsensorsserver| Detach complete
[INFO] Executing detach action, level 15 on device waist-inertials_wrapper with parameters []
[DEBUG] |yarp.device.multipleanalogsensorsserver| Detach complete
[INFO] Executing detach action, level 15 on device left_foot-IMU_wrapper with parameters []
[DEBUG] |yarp.device.multipleanalogsensorsserver| Detach complete
[INFO] Executing detach action, level 15 on device right_foot-IMU_wrapper with parameters []
[DEBUG] |yarp.device.multipleanalogsensorsserver| Detach complete
[INFO] Executing detach action, level 15 on device alljoints-inertials_wrapper with parameters []
[DEBUG] |yarp.device.multipleanalogsensorsserver| Detach complete
[INFO] All actions for action level 15 of shutdown phase started. Waiting for unfinished actions.
[INFO] All actions for action level 15 of shutdown phase finished.
[INFO] Entering action level 20 of phase shutdown
[INFO] Executing detach action, level 20 on device left_arm-mc_remapper with parameters []
[INFO] Executing detach action, level 20 on device right_arm-mc_remapper with parameters []
[INFO] Executing detach action, level 20 on device left_leg-mc_remapper with parameters []
[INFO] Executing detach action, level 20 on device right_leg-mc_remapper with parameters []
[INFO] Executing detach action, level 20 on device head-mc_remapper with parameters []
[INFO] Executing detach action, level 20 on device torso-mc_remapper with parameters []
[INFO] Executing detach action, level 20 on device left_leg-FT_remapper with parameters []
[INFO] Executing detach action, level 20 on device right_leg-FT_remapper with parameters []
[INFO] Executing detach action, level 20 on device left_foot-IMU_remapper with parameters []
[INFO] Executing detach action, level 20 on device right_foot-IMU_remapper with parameters []
[INFO] Executing detach action, level 20 on device alljoints-inertials_remapper with parameters []
[INFO] All actions for action level 20 of shutdown phase started. Waiting for unfinished actions.
[INFO] All actions for action level 20 of shutdown phase finished.

[INFO] File is a URI:  model://ergoCub/conf/gazebo_ergocub_waist_inertial.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/gazebo_ergocub_waist_inertial.ini
[INFO] gz-sim-yarp-imu-system: configuration of sensor  waist_imu_0  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_imu| Parameters are (device gazebo_imu) (disableImplicitNetworkWrapper) (parentLinkName torso_1) (sensorName waist_imu_0) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/link/torso_1/sensor/waist_imu_0") (sensor_name waist_imu_0) (yarpDeviceName waist_inertial_hardware_device)
[INFO] |yarp.dev.PolyDriver|gazebo_imu| Created device <gazebo_imu>. See C++ class IMUDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/waist_inertial_hardware_device
[INFO] File is a URI:  model://ergoCub/conf/FT/gazebo_ergocub_left_arm_ft.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/FT/gazebo_ergocub_left_arm_ft.ini
[INFO] gz-sim-yarp-forcetorque-system: configuration of sensor  l_arm_ft  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_forcetorque| Parameters are (device gazebo_forcetorque) (disableImplicitNetworkWrapper) (jointName l_arm_ft_sensor) (sensorName l_arm_ft) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/joint/l_arm_ft_sensor/sensor/l_arm_ft") (sensor_name l_arm_ft) (yarpDeviceName ergocub_left_arm_ft)
[INFO] |yarp.dev.PolyDriver|gazebo_forcetorque| Created device <gazebo_forcetorque>. See C++ class ForceTorqueDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/ergocub_left_arm_ft
[INFO] File is a URI:  model://ergoCub/conf/FT/gazebo_ergocub_right_arm_ft.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/FT/gazebo_ergocub_right_arm_ft.ini
[INFO] gz-sim-yarp-forcetorque-system: configuration of sensor  r_arm_ft  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_forcetorque| Parameters are (device gazebo_forcetorque) (disableImplicitNetworkWrapper) (jointName r_arm_ft_sensor) (sensorName r_arm_ft) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/joint/r_arm_ft_sensor/sensor/r_arm_ft") (sensor_name r_arm_ft) (yarpDeviceName ergocub_right_arm_ft)
[INFO] |yarp.dev.PolyDriver|gazebo_forcetorque| Created device <gazebo_forcetorque>. See C++ class ForceTorqueDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/ergocub_right_arm_ft
[INFO] File is a URI:  model://ergoCub/conf/gazebo_ergocub_l_arm_ft_sensor_inertial.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/gazebo_ergocub_l_arm_ft_sensor_inertial.ini
[INFO] gz-sim-yarp-imu-system: configuration of sensor  l_arm_ft_imu  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_imu| Parameters are (device gazebo_imu) (disableImplicitNetworkWrapper) (parentLinkName l_shoulder_3) (sensorName l_arm_ft_imu) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/link/l_shoulder_3/sensor/l_arm_ft_imu") (sensor_name l_arm_ft_imu) (yarpDeviceName l_arm_ft_sensor_inertial_hardware_device)
[INFO] |yarp.dev.PolyDriver|gazebo_imu| Created device <gazebo_imu>. See C++ class IMUDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/l_arm_ft_sensor_inertial_hardware_device
[INFO] File is a URI:  model://ergoCub/conf/gazebo_ergocub_r_arm_ft_sensor_inertial.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/gazebo_ergocub_r_arm_ft_sensor_inertial.ini
[INFO] gz-sim-yarp-imu-system: configuration of sensor  r_arm_ft_imu  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_imu| Parameters are (device gazebo_imu) (disableImplicitNetworkWrapper) (parentLinkName r_shoulder_3) (sensorName r_arm_ft_imu) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/link/r_shoulder_3/sensor/r_arm_ft_imu") (sensor_name r_arm_ft_imu) (yarpDeviceName r_arm_ft_sensor_inertial_hardware_device)
[INFO] |yarp.dev.PolyDriver|gazebo_imu| Created device <gazebo_imu>. See C++ class IMUDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/r_arm_ft_sensor_inertial_hardware_device
[INFO] File is a URI:  model://ergoCub/conf/FT/gazebo_ergocub_left_leg_ft.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/FT/gazebo_ergocub_left_leg_ft.ini
[INFO] gz-sim-yarp-forcetorque-system: configuration of sensor  l_leg_ft  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_forcetorque| Parameters are (device gazebo_forcetorque) (disableImplicitNetworkWrapper) (jointName l_leg_ft_sensor) (sensorName l_leg_ft) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/joint/l_leg_ft_sensor/sensor/l_leg_ft") (sensor_name l_leg_ft) (yarpDeviceName ergocub_left_leg_ft)
[INFO] |yarp.dev.PolyDriver|gazebo_forcetorque| Created device <gazebo_forcetorque>. See C++ class ForceTorqueDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/ergocub_left_leg_ft
[INFO] File is a URI:  model://ergoCub/conf/FT/gazebo_ergocub_left_foot_front_ft.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/FT/gazebo_ergocub_left_foot_front_ft.ini
[INFO] gz-sim-yarp-forcetorque-system: configuration of sensor  l_foot_front_ft  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_forcetorque| Parameters are (device gazebo_forcetorque) (disableImplicitNetworkWrapper) (jointName l_foot_front_ft_sensor) (sensorName l_foot_front_ft) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/joint/l_foot_front_ft_sensor/sensor/l_foot_front_ft") (sensor_name l_foot_front_ft) (yarpDeviceName ergocub_left_foot_front_ft)
[INFO] |yarp.dev.PolyDriver|gazebo_forcetorque| Created device <gazebo_forcetorque>. See C++ class ForceTorqueDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/ergocub_left_foot_front_ft
[INFO] File is a URI:  model://ergoCub/conf/FT/gazebo_ergocub_left_foot_rear_ft.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/FT/gazebo_ergocub_left_foot_rear_ft.ini
[INFO] gz-sim-yarp-forcetorque-system: configuration of sensor  l_foot_rear_ft  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_forcetorque| Parameters are (device gazebo_forcetorque) (disableImplicitNetworkWrapper) (jointName l_foot_rear_ft_sensor) (sensorName l_foot_rear_ft) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/joint/l_foot_rear_ft_sensor/sensor/l_foot_rear_ft") (sensor_name l_foot_rear_ft) (yarpDeviceName ergocub_left_foot_rear_ft)
[INFO] |yarp.dev.PolyDriver|gazebo_forcetorque| Created device <gazebo_forcetorque>. See C++ class ForceTorqueDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/ergocub_left_foot_rear_ft
[INFO] File is a URI:  model://ergoCub/conf/gazebo_ergocub_l_foot_front_ft_sensor_inertial.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/gazebo_ergocub_l_foot_front_ft_sensor_inertial.ini
[INFO] gz-sim-yarp-imu-system: configuration of sensor  l_foot_front_ft_imu  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_imu| Parameters are (device gazebo_imu) (disableImplicitNetworkWrapper) (parentLinkName l_foot_front) (sensorName l_foot_front_ft_imu) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/link/l_foot_front/sensor/l_foot_front_ft_imu") (sensor_name l_foot_front_ft_imu) (yarpDeviceName l_foot_front_ft_sensor_inertial_hardware_device)
[INFO] |yarp.dev.PolyDriver|gazebo_imu| Created device <gazebo_imu>. See C++ class IMUDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/l_foot_front_ft_sensor_inertial_hardware_device
[INFO] File is a URI:  model://ergoCub/conf/gazebo_ergocub_l_foot_rear_ft_sensor_inertial.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/gazebo_ergocub_l_foot_rear_ft_sensor_inertial.ini
[INFO] gz-sim-yarp-imu-system: configuration of sensor  l_foot_rear_ft_imu  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_imu| Parameters are (device gazebo_imu) (disableImplicitNetworkWrapper) (parentLinkName l_foot_rear) (sensorName l_foot_rear_ft_imu) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/link/l_foot_rear/sensor/l_foot_rear_ft_imu") (sensor_name l_foot_rear_ft_imu) (yarpDeviceName l_foot_rear_ft_sensor_inertial_hardware_device)
[INFO] |yarp.dev.PolyDriver|gazebo_imu| Created device <gazebo_imu>. See C++ class IMUDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/l_foot_rear_ft_sensor_inertial_hardware_device
[INFO] File is a URI:  model://ergoCub/conf/gazebo_ergocub_l_leg_ft_sensor_inertial.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/gazebo_ergocub_l_leg_ft_sensor_inertial.ini
[INFO] gz-sim-yarp-imu-system: configuration of sensor  l_leg_ft_imu  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_imu| Parameters are (device gazebo_imu) (disableImplicitNetworkWrapper) (parentLinkName l_hip_3) (sensorName l_leg_ft_imu) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/link/l_hip_3/sensor/l_leg_ft_imu") (sensor_name l_leg_ft_imu) (yarpDeviceName l_leg_ft_sensor_inertial_hardware_device)
[INFO] |yarp.dev.PolyDriver|gazebo_imu| Created device <gazebo_imu>. See C++ class IMUDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/l_leg_ft_sensor_inertial_hardware_device
[INFO] File is a URI:  model://ergoCub/conf/FT/gazebo_ergocub_right_leg_ft.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/FT/gazebo_ergocub_right_leg_ft.ini
[INFO] gz-sim-yarp-forcetorque-system: configuration of sensor  r_leg_ft  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_forcetorque| Parameters are (device gazebo_forcetorque) (disableImplicitNetworkWrapper) (jointName r_leg_ft_sensor) (sensorName r_leg_ft) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/joint/r_leg_ft_sensor/sensor/r_leg_ft") (sensor_name r_leg_ft) (yarpDeviceName ergocub_right_leg_ft)
[INFO] |yarp.dev.PolyDriver|gazebo_forcetorque| Created device <gazebo_forcetorque>. See C++ class ForceTorqueDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/ergocub_right_leg_ft
[INFO] File is a URI:  model://ergoCub/conf/FT/gazebo_ergocub_right_foot_front_ft.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/FT/gazebo_ergocub_right_foot_front_ft.ini
[INFO] gz-sim-yarp-forcetorque-system: configuration of sensor  r_foot_front_ft  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_forcetorque| Parameters are (device gazebo_forcetorque) (disableImplicitNetworkWrapper) (jointName r_foot_front_ft_sensor) (sensorName r_foot_front_ft) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/joint/r_foot_front_ft_sensor/sensor/r_foot_front_ft") (sensor_name r_foot_front_ft) (yarpDeviceName ergocub_right_foot_front_ft)
[INFO] |yarp.dev.PolyDriver|gazebo_forcetorque| Created device <gazebo_forcetorque>. See C++ class ForceTorqueDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/ergocub_right_foot_front_ft
[INFO] File is a URI:  model://ergoCub/conf/FT/gazebo_ergocub_right_foot_rear_ft.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/FT/gazebo_ergocub_right_foot_rear_ft.ini
[INFO] gz-sim-yarp-forcetorque-system: configuration of sensor  r_foot_rear_ft  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_forcetorque| Parameters are (device gazebo_forcetorque) (disableImplicitNetworkWrapper) (jointName r_foot_rear_ft_sensor) (sensorName r_foot_rear_ft) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/joint/r_foot_rear_ft_sensor/sensor/r_foot_rear_ft") (sensor_name r_foot_rear_ft) (yarpDeviceName ergocub_right_foot_rear_ft)
[INFO] |yarp.dev.PolyDriver|gazebo_forcetorque| Created device <gazebo_forcetorque>. See C++ class ForceTorqueDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/ergocub_right_foot_rear_ft
[INFO] File is a URI:  model://ergoCub/conf/gazebo_ergocub_r_foot_front_ft_sensor_inertial.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/gazebo_ergocub_r_foot_front_ft_sensor_inertial.ini
[INFO] gz-sim-yarp-imu-system: configuration of sensor  r_foot_front_ft_imu  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_imu| Parameters are (device gazebo_imu) (disableImplicitNetworkWrapper) (parentLinkName r_foot_front) (sensorName r_foot_front_ft_imu) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/link/r_foot_front/sensor/r_foot_front_ft_imu") (sensor_name r_foot_front_ft_imu) (yarpDeviceName r_foot_front_ft_sensor_inertial_hardware_device)
[INFO] |yarp.dev.PolyDriver|gazebo_imu| Created device <gazebo_imu>. See C++ class IMUDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/r_foot_front_ft_sensor_inertial_hardware_device
[INFO] File is a URI:  model://ergoCub/conf/gazebo_ergocub_r_foot_rear_ft_sensor_inertial.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/gazebo_ergocub_r_foot_rear_ft_sensor_inertial.ini
[INFO] gz-sim-yarp-imu-system: configuration of sensor  r_foot_rear_ft_imu  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_imu| Parameters are (device gazebo_imu) (disableImplicitNetworkWrapper) (parentLinkName r_foot_rear) (sensorName r_foot_rear_ft_imu) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/link/r_foot_rear/sensor/r_foot_rear_ft_imu") (sensor_name r_foot_rear_ft_imu) (yarpDeviceName r_foot_rear_ft_sensor_inertial_hardware_device)
[INFO] |yarp.dev.PolyDriver|gazebo_imu| Created device <gazebo_imu>. See C++ class IMUDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/r_foot_rear_ft_sensor_inertial_hardware_device
[INFO] File is a URI:  model://ergoCub/conf/gazebo_ergocub_r_leg_ft_sensor_inertial.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/gazebo_ergocub_r_leg_ft_sensor_inertial.ini
[INFO] gz-sim-yarp-imu-system: configuration of sensor  r_leg_ft_imu  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_imu| Parameters are (device gazebo_imu) (disableImplicitNetworkWrapper) (parentLinkName r_hip_3) (sensorName r_leg_ft_imu) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/link/r_hip_3/sensor/r_leg_ft_imu") (sensor_name r_leg_ft_imu) (yarpDeviceName r_leg_ft_sensor_inertial_hardware_device)
[INFO] |yarp.dev.PolyDriver|gazebo_imu| Created device <gazebo_imu>. See C++ class IMUDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/r_leg_ft_sensor_inertial_hardware_device
[INFO] File is a URI:  model://ergoCub/conf/gazebo_ergocub_inertial.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/gazebo_ergocub_inertial.ini
[INFO] gz-sim-yarp-imu-system: configuration of sensor  head_imu_0  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_imu| Parameters are (device gazebo_imu) (disableImplicitNetworkWrapper) (parentLinkName head) (sensorName head_imu_0) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/link/head/sensor/head_imu_0") (sensor_name head_imu_0) (yarpDeviceName head_inertial_hardware_device)
[INFO] |yarp.dev.PolyDriver|gazebo_imu| Created device <gazebo_imu>. See C++ class IMUDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/head_inertial_hardware_device
[INFO] File is a URI:  model://ergoCub/conf/gazebo_ergocub_realsense_inertial.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/gazebo_ergocub_realsense_inertial.ini
[INFO] gz-sim-yarp-imu-system: configuration of sensor  realsense_imu_0  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_imu| Parameters are (device gazebo_imu) (disableImplicitNetworkWrapper) (parentLinkName realsense) (sensorName realsense_imu_0) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/link/realsense/sensor/realsense_imu_0") (sensor_name realsense_imu_0) (yarpDeviceName realsense_inertial_hardware_device)
[INFO] |yarp.dev.PolyDriver|gazebo_imu| Created device <gazebo_imu>. See C++ class IMUDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/realsense_inertial_hardware_device
[INFO] File is a URI:  model://ergoCub/conf/sensors/gazebo_ergocub_lidar.ini
[INFO] Yarp configuration file loaded:  /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/sensors/gazebo_ergocub_lidar.ini
[INFO] gz-sim-yarp-laser-system: configuration of sensor  lasersensor_head  loaded
[DEBUG] |yarp.dev.PolyDriver|gazebo_laser| Parameters are (SENSOR (max_distance 5.0) (min_distance 0.200000000000000011102) (max_angle 360) (min_angle 0) (resolution 0.5) (allow_infinity 1)) (device gazebo_laser) (disableImplicitNetworkWrapper) (parentLinkName head) (period 10) (sensorName lasersensor_head) (sensorScopedName "world/tutorial_controlboard/model/ergoCub/link/head/sensor/lasersensor_head") (sensor_name lasersensor_head) (yarpDeviceName las360)
[INFO] |yarp.devices.Lidar2DDeviceBase| Using the following parameters:
[INFO] |yarp.devices.Lidar2DDeviceBase| max_dist: 5  min_dist: 0.2
[INFO] |yarp.devices.Lidar2DDeviceBase| max_angle: 360  min_angle: 0
[INFO] |yarp.devices.Lidar2DDeviceBase| resolution: 0.5
[INFO] |yarp.devices.Lidar2DDeviceBase| sensors: 720
[INFO] |yarp.devices.Lidar2DDeviceBase| allow_infinity: true
[INFO] |yarp.dev.PolyDriver|gazebo_laser| Created device <gazebo_laser>. See C++ class LaserDriver for documentation.
[INFO] Registered YARP device with instance name: world/tutorial_controlboard/model/ergoCub/las360
[INFO] File is a URI:  model://ergoCub/conf/ergocub_gz_sim.xml
[DEBUG] Reading file /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/ergocub_gz_sim.xml
[DEBUG] yarprobotinterface: using xml parser for DTD v3.x
[DEBUG] Reading file /home/lomoretti/robotology/robotology-superbuild/build/install/share/ergoCub/conf/ergocub_gz_sim.xml
[INFO] Yarprobotinterface was started using the following enable_tags:
[INFO] Yarprobotinterface was started using the following disable_tags:
[DEBUG] List of all enable attributes found in the include tags:
[DEBUG] List of all disable attributes found in the include tags:
[DEBUG] Preprocessor complete in:  0.000509739 s
[INFO] startup phase starting...
[INFO] Opening device left_arm-mc_nws_yarp with parameters [("robotName" = "/ergocubSim"), ("name" = "/ergocubSim/left_arm"), ("period" = "0.01")]
[DEBUG] |yarp.dev.PolyDriver|left_arm-mc_nws_yarp| Parameters are (device controlBoard_nws_yarp) (id left_arm-mc_nws_yarp) (name "/ergocubSim/left_arm") (period 0.0100000000000000002082) (robotName "/ergocubSim")
[INFO] |yarp.os.Port|/ergocubSim/left_arm/rpc:i| Port /ergocubSim/left_arm/rpc:i active at tcp://<IP_ADDRESS>:10003/
[INFO] |yarp.os.Port|/ergocubSim/left_arm/command:i| Port /ergocubSim/left_arm/command:i active at tcp://<IP_ADDRESS>:10004/
[INFO] |yarp.os.Port|/ergocubSim/left_arm/state:o| Port /ergocubSim/left_arm/state:o active at tcp://<IP_ADDRESS>:10005/
[INFO] |yarp.os.Port|/ergocubSim/left_arm/stateExt:o| Port /ergocubSim/left_arm/stateExt:o active at tcp://<IP_ADDRESS>:10006/
[INFO] |yarp.dev.PolyDriver|left_arm-mc_nws_yarp| Created wrapper <controlBoard_nws_yarp>. See C++ class ControlBoard_nws_yarp for documentation.
[INFO] Opening device right_arm-mc_nws_yarp with parameters [("robotName" = "/ergocubSim"), ("name" = "/ergocubSim/right_arm"), ("period" = "0.01")]
[DEBUG] |yarp.dev.PolyDriver|right_arm-mc_nws_yarp| Parameters are (device controlBoard_nws_yarp) (id right_arm-mc_nws_yarp) (name "/ergocubSim/right_arm") (period 0.0100000000000000002082) (robotName "/ergocubSim")
[INFO] |yarp.os.Port|/ergocubSim/right_arm/rpc:i| Port /ergocubSim/right_arm/rpc:i active at tcp://<IP_ADDRESS>:10007/
[INFO] |yarp.os.Port|/ergocubSim/right_arm/command:i| Port /ergocubSim/right_arm/command:i active at tcp://<IP_ADDRESS>:10008/
[INFO] |yarp.os.Port|/ergocubSim/right_arm/state:o| Port /ergocubSim/right_arm/state:o active at tcp://<IP_ADDRESS>:10009/
[INFO] |yarp.os.Port|/ergocubSim/right_arm/stateExt:o| Port /ergocubSim/right_arm/stateExt:o active at tcp://<IP_ADDRESS>:10010/
[INFO] |yarp.dev.PolyDriver|right_arm-mc_nws_yarp| Created wrapper <controlBoard_nws_yarp>. See C++ class ControlBoard_nws_yarp for documentation.
[INFO] Opening device left_leg-mc_nws_yarp with parameters [("robotName" = "/ergocubSim"), ("name" = "/ergocubSim/left_leg"), ("period" = "0.01")]
[DEBUG] |yarp.dev.PolyDriver|left_leg-mc_nws_yarp| Parameters are (device controlBoard_nws_yarp) (id left_leg-mc_nws_yarp) (name "/ergocubSim/left_leg") (period 0.0100000000000000002082) (robotName "/ergocubSim")
[INFO] |yarp.os.Port|/ergocubSim/left_leg/rpc:i| Port /ergocubSim/left_leg/rpc:i active at tcp://<IP_ADDRESS>:10011/
[INFO] |yarp.os.Port|/ergocubSim/left_leg/command:i| Port /ergocubSim/left_leg/command:i active at tcp://<IP_ADDRESS>:10012/
[INFO] |yarp.os.Port|/ergocubSim/left_leg/state:o| Port /ergocubSim/left_leg/state:o active at tcp://<IP_ADDRESS>:10013/
[INFO] |yarp.os.Port|/ergocubSim/left_leg/stateExt:o| Port /ergocubSim/left_leg/stateExt:o active at tcp://<IP_ADDRESS>:10014/
[INFO] |yarp.dev.PolyDriver|left_leg-mc_nws_yarp| Created wrapper <controlBoard_nws_yarp>. See C++ class ControlBoard_nws_yarp for documentation.
[INFO] Opening device right_leg-mc_nws_yarp with parameters [("robotName" = "/ergocubSim"), ("name" = "/ergocubSim/right_leg"), ("period" = "0.01")]
[DEBUG] |yarp.dev.PolyDriver|right_leg-mc_nws_yarp| Parameters are (device controlBoard_nws_yarp) (id right_leg-mc_nws_yarp) (name "/ergocubSim/right_leg") (period 0.0100000000000000002082) (robotName "/ergocubSim")
[INFO] |yarp.os.Port|/ergocubSim/right_leg/rpc:i| Port /ergocubSim/right_leg/rpc:i active at tcp://<IP_ADDRESS>:10015/
[INFO] |yarp.os.Port|/ergocubSim/right_leg/command:i| Port /ergocubSim/right_leg/command:i active at tcp://<IP_ADDRESS>:10016/
[INFO] |yarp.os.Port|/ergocubSim/right_leg/state:o| Port /ergocubSim/right_leg/state:o active at tcp://<IP_ADDRESS>:10017/
[INFO] |yarp.os.Port|/ergocubSim/right_leg/stateExt:o| Port /ergocubSim/right_leg/stateExt:o active at tcp://<IP_ADDRESS>:10018/
[INFO] |yarp.dev.PolyDriver|right_leg-mc_nws_yarp| Created wrapper <controlBoard_nws_yarp>. See C++ class ControlBoard_nws_yarp for documentation.
[INFO] Opening device head-mc_nws_yarp with parameters [("robotName" = "/ergocubSim"), ("name" = "/ergocubSim/head")]
[DEBUG] |yarp.dev.PolyDriver|head-mc_nws_yarp| Parameters are (device controlBoard_nws_yarp) (id head-mc_nws_yarp) (name "/ergocubSim/head") (robotName "/ergocubSim")
[DEBUG] |yarp.devices.controlBoard_nws_yarp| 'period' parameter missing, using default thread period = 0.02s
[INFO] |yarp.os.Port|/ergocubSim/head/rpc:i| Port /ergocubSim/head/rpc:i active at tcp://<IP_ADDRESS>:10019/
[INFO] |yarp.os.Port|/ergocubSim/head/command:i| Port /ergocubSim/head/command:i active at tcp://<IP_ADDRESS>:10020/
[INFO] |yarp.os.Port|/ergocubSim/head/state:o| Port /ergocubSim/head/state:o active at tcp://<IP_ADDRESS>:10021/
[INFO] |yarp.os.Port|/ergocubSim/head/stateExt:o| Port /ergocubSim/head/stateExt:o active at tcp://<IP_ADDRESS>:10022/
[INFO] |yarp.dev.PolyDriver|head-mc_nws_yarp| Created wrapper <controlBoard_nws_yarp>. See C++ class ControlBoard_nws_yarp for documentation.
[INFO] Opening device torso-mc_nws_yarp with parameters [("robotName" = "/ergocubSim"), ("name" = "/ergocubSim/torso"), ("period" = "0.01")]
[DEBUG] |yarp.dev.PolyDriver|torso-mc_nws_yarp| Parameters are (device controlBoard_nws_yarp) (id torso-mc_nws_yarp) (name "/ergocubSim/torso") (period 0.0100000000000000002082) (robotName "/ergocubSim")
[INFO] |yarp.os.Port|/ergocubSim/torso/rpc:i| Port /ergocubSim/torso/rpc:i active at tcp://<IP_ADDRESS>:10023/
[INFO] |yarp.os.Port|/ergocubSim/torso/command:i| Port /ergocubSim/torso/command:i active at tcp://<IP_ADDRESS>:10024/
[INFO] |yarp.os.Port|/ergocubSim/torso/state:o| Port /ergocubSim/torso/state:o active at tcp://<IP_ADDRESS>:10025/
[INFO] |yarp.os.Port|/ergocubSim/torso/stateExt:o| Port /ergocubSim/torso/stateExt:o active at tcp://<IP_ADDRESS>:10026/
[INFO] |yarp.dev.PolyDriver|torso-mc_nws_yarp| Created wrapper <controlBoard_nws_yarp>. See C++ class ControlBoard_nws_yarp for documentation.
[INFO] Opening device left_arm-mc_remapper with parameters [("robotName" = "/ergocubSim"), ("networks" = "(left_arm_joints1)"), ("left_arm_joints1" = "( 0 6 0 6 )"), ("joints" = "7")]
[DEBUG] |yarp.dev.PolyDriver|left_arm-mc_remapper| Parameters are (device controlboardremapper) (id left_arm-mc_remapper) (joints 7) (left_arm_joints1 (0 6 0 6)) (networks (left_arm_joints1)) (robotName "/ergocubSim")
[INFO] |yarp.dev.PolyDriver|left_arm-mc_remapper| Created device <controlboardremapper>. See C++ class ControlBoardRemapper for documentation.
[INFO] Opening device right_arm-mc_remapper with parameters [("robotName" = "/ergocubSim"), ("networks" = "(right_arm_joints1)"), ("right_arm_joints1" = "( 0 6 0 6 )"), ("joints" = "7")]
[DEBUG] |yarp.dev.PolyDriver|right_arm-mc_remapper| Parameters are (device controlboardremapper) (id right_arm-mc_remapper) (joints 7) (networks (right_arm_joints1)) (right_arm_joints1 (0 6 0 6)) (robotName "/ergocubSim")
[INFO] |yarp.dev.PolyDriver|right_arm-mc_remapper| Created device <controlboardremapper>. See C++ class ControlBoardRemapper for documentation.
[INFO] Opening device left_leg-mc_remapper with parameters [("robotName" = "/ergocubSim"), ("networks" = "(left_leg_joints1)"), ("left_leg_joints1" = "( 0 5 0 5 )"), ("joints" = "6")]
[DEBUG] |yarp.dev.PolyDriver|left_leg-mc_remapper| Parameters are (device controlboardremapper) (id left_leg-mc_remapper) (joints 6) (left_leg_joints1 (0 5 0 5)) (networks (left_leg_joints1)) (robotName "/ergocubSim")
[INFO] |yarp.dev.PolyDriver|left_leg-mc_remapper| Created device <controlboardremapper>. See C++ class ControlBoardRemapper for documentation.
[INFO] Opening device right_leg-mc_remapper with parameters [("robotName" = "/ergocubSim"), ("networks" = "(right_leg_joints1)"), ("right_leg_joints1" = "( 0 5 0 5 )"), ("joints" = "6")]
[DEBUG] |yarp.dev.PolyDriver|right_leg-mc_remapper| Parameters are (device controlboardremapper) (id right_leg-mc_remapper) (joints 6) (networks (right_leg_joints1)) (right_leg_joints1 (0 5 0 5)) (robotName "/ergocubSim")
[INFO] |yarp.dev.PolyDriver|right_leg-mc_remapper| Created device <controlboardremapper>. See C++ class ControlBoardRemapper for documentation.
[INFO] Opening device head-mc_remapper with parameters [("robotName" = "/ergocubSim"), ("networks" = "(head_joints1)"), ("head_joints1" = "( 0 3 0 3 )"), ("joints" = "4")]
[DEBUG] |yarp.dev.PolyDriver|head-mc_remapper| Parameters are (device controlboardremapper) (head_joints1 (0 3 0 3)) (id head-mc_remapper) (joints 4) (networks (head_joints1)) (robotName "/ergocubSim")
[INFO] |yarp.dev.PolyDriver|head-mc_remapper| Created device <controlboardremapper>. See C++ class ControlBoardRemapper for documentation.
[INFO] Opening device torso-mc_remapper with parameters [("robotName" = "/ergocubSim"), ("networks" = "(torso_joints)"), ("torso_joints" = "( 0 2 0 2 )"), ("joints" = "3")]
[DEBUG] |yarp.dev.PolyDriver|torso-mc_remapper| Parameters are (device controlboardremapper) (id torso-mc_remapper) (joints 3) (networks (torso_joints)) (robotName "/ergocubSim") (torso_joints (0 2 0 2))
[INFO] |yarp.dev.PolyDriver|torso-mc_remapper| Created device <controlboardremapper>. See C++ class ControlBoardRemapper for documentation.
[INFO] Opening device left_leg-FT_remapper with parameters [("robotName" = "/ergocubSim"), ("SixAxisForceTorqueSensorsNames" = "(l_leg_ft l_foot_rear_ft l_foot_front_ft)"), ("TemperatureSensorsNames" = "(l_leg_ft l_foot_rear_ft l_foot_front_ft)")]
[DEBUG] |yarp.dev.PolyDriver|left_leg-FT_remapper| Parameters are (SixAxisForceTorqueSensorsNames (l_leg_ft l_foot_rear_ft l_foot_front_ft)) (TemperatureSensorsNames (l_leg_ft l_foot_rear_ft l_foot_front_ft)) (device multipleanalogsensorsremapper) (id left_leg-FT_remapper) (robotName "/ergocubSim")
[INFO] |yarp.dev.PolyDriver|left_leg-FT_remapper| Created device <multipleanalogsensorsremapper>. See C++ class MultipleAnalogSensorsRemapper for documentation.
[INFO] Opening device right_leg-FT_remapper with parameters [("robotName" = "/ergocubSim"), ("SixAxisForceTorqueSensorsNames" = "(r_leg_ft r_foot_rear_ft r_foot_front_ft)"), ("TemperatureSensorsNames" = "(r_leg_ft r_foot_rear_ft r_foot_front_ft)")]
[DEBUG] |yarp.dev.PolyDriver|right_leg-FT_remapper| Parameters are (SixAxisForceTorqueSensorsNames (r_leg_ft r_foot_rear_ft r_foot_front_ft)) (TemperatureSensorsNames (r_leg_ft r_foot_rear_ft r_foot_front_ft)) (device multipleanalogsensorsremapper) (id right_leg-FT_remapper) (robotName "/ergocubSim")
[INFO] |yarp.dev.PolyDriver|right_leg-FT_remapper| Created device <multipleanalogsensorsremapper>. See C++ class MultipleAnalogSensorsRemapper for documentation.
[INFO] Opening device left_leg-FT_wrapper with parameters [("robotName" = "/ergocubSim"), ("period" = "10"), ("name" = "/ergocubSim/left_leg/FT")]
[DEBUG] |yarp.dev.PolyDriver|left_leg-FT_wrapper| Parameters are (device multipleanalogsensorsserver) (id left_leg-FT_wrapper) (name "/ergocubSim/left_leg/FT") (period 10) (robotName "/ergocubSim")
[DEBUG] |yarp.device.multipleanalogsensorsserver| Open complete
[INFO] |yarp.dev.PolyDriver|left_leg-FT_wrapper| Created wrapper <multipleanalogsensorsserver>. See C++ class MultipleAnalogSensorsServer for documentation.
[INFO] Opening device right_leg-FT_wrapper with parameters [("robotName" = "/ergocubSim"), ("period" = "10"), ("name" = "/ergocubSim/right_leg/FT")]
[DEBUG] |yarp.dev.PolyDriver|right_leg-FT_wrapper| Parameters are (device multipleanalogsensorsserver) (id right_leg-FT_wrapper) (name "/ergocubSim/right_leg/FT") (period 10) (robotName "/ergocubSim")
[DEBUG] |yarp.device.multipleanalogsensorsserver| Open complete
[INFO] |yarp.dev.PolyDriver|right_leg-FT_wrapper| Created wrapper <multipleanalogsensorsserver>. See C++ class MultipleAnalogSensorsServer for documentation.
[INFO] Opening device left_arm-FT_wrapper with parameters [("robotName" = "/ergocubSim"), ("period" = "10"), ("name" = "/ergocubSim/left_arm/FT")]
[DEBUG] |yarp.dev.PolyDriver|left_arm-FT_wrapper| Parameters are (device multipleanalogsensorsserver) (id left_arm-FT_wrapper) (name "/ergocubSim/left_arm/FT") (period 10) (robotName "/ergocubSim")
[DEBUG] |yarp.device.multipleanalogsensorsserver| Open complete
[INFO] |yarp.dev.PolyDriver|left_arm-FT_wrapper| Created wrapper <multipleanalogsensorsserver>. See C++ class MultipleAnalogSensorsServer for documentation.
[INFO] Opening device right_arm-FT_wrapper with parameters [("robotName" = "/ergocubSim"), ("period" = "10"), ("name" = "/ergocubSim/right_arm/FT")]
[DEBUG] |yarp.dev.PolyDriver|right_arm-FT_wrapper| Parameters are (device multipleanalogsensorsserver) (id right_arm-FT_wrapper) (name "/ergocubSim/right_arm/FT") (period 10) (robotName "/ergocubSim")
[DEBUG] |yarp.device.multipleanalogsensorsserver| Open complete
[INFO] |yarp.dev.PolyDriver|right_arm-FT_wrapper| Created wrapper <multipleanalogsensorsserver>. See C++ class MultipleAnalogSensorsServer for documentation.
[INFO] Opening device head-inertials_wrapper with parameters [("robotName" = "/ergocubSim"), ("period" = "10"), ("name" = "/ergocubSim/head/inertials")]
[DEBUG] |yarp.dev.PolyDriver|head-inertials_wrapper| Parameters are (device multipleanalogsensorsserver) (id head-inertials_wrapper) (name "/ergocubSim/head/inertials") (period 10) (robotName "/ergocubSim")
[DEBUG] |yarp.device.multipleanalogsensorsserver| Open complete
[INFO] |yarp.dev.PolyDriver|head-inertials_wrapper| Created wrapper <multipleanalogsensorsserver>. See C++ class MultipleAnalogSensorsServer for documentation.
[INFO] Opening device waist-inertials_wrapper with parameters [("robotName" = "/ergocubSim"), ("period" = "10"), ("name" = "/ergocubSim/waist/inertials")]
[DEBUG] |yarp.dev.PolyDriver|waist-inertials_wrapper| Parameters are (device multipleanalogsensorsserver) (id waist-inertials_wrapper) (name "/ergocubSim/waist/inertials") (period 10) (robotName "/ergocubSim")
[DEBUG] |yarp.device.multipleanalogsensorsserver| Open complete
[INFO] |yarp.dev.PolyDriver|waist-inertials_wrapper| Created wrapper <multipleanalogsensorsserver>. See C++ class MultipleAnalogSensorsServer for documentation.
[INFO] Opening device left_foot-IMU_remapper with parameters [("robotName" = "/ergocubSim"), ("ThreeAxisGyroscopesNames" = "(l_foot_front_ft_imu, l_foot_rear_ft_imu)"), ("ThreeAxisLinearAccelerometersNames" = "(l_foot_front_ft_imu, l_foot_rear_ft_imu)"), ("ThreeAxisMagnetometersNames" = "(l_foot_front_ft_imu, l_foot_rear_ft_imu)"), ("OrientationSensorsNames" = "(l_foot_front_ft_imu, l_foot_rear_ft_imu)")]
[DEBUG] |yarp.dev.PolyDriver|left_foot-IMU_remapper| Parameters are (OrientationSensorsNames (l_foot_front_ft_imu l_foot_rear_ft_imu)) (ThreeAxisGyroscopesNames (l_foot_front_ft_imu l_foot_rear_ft_imu)) (ThreeAxisLinearAccelerometersNames (l_foot_front_ft_imu l_foot_rear_ft_imu)) (ThreeAxisMagnetometersNames (l_foot_front_ft_imu l_foot_rear_ft_imu)) (device multipleanalogsensorsremapper) (id left_foot-IMU_remapper) (robotName "/ergocubSim")
[INFO] |yarp.dev.PolyDriver|left_foot-IMU_remapper| Created device <multipleanalogsensorsremapper>. See C++ class MultipleAnalogSensorsRemapper for documentation.
[INFO] Opening device left_foot-IMU_wrapper with parameters [("robotName" = "/ergocubSim"), ("period" = "10"), ("name" = "/ergocubSim/left_foot_heel_tiptoe/imu")]
[DEBUG] |yarp.dev.PolyDriver|left_foot-IMU_wrapper| Parameters are (device multipleanalogsensorsserver) (id left_foot-IMU_wrapper) (name "/ergocubSim/left_foot_heel_tiptoe/imu") (period 10) (robotName "/ergocubSim")
[DEBUG] |yarp.device.multipleanalogsensorsserver| Open complete
[INFO] |yarp.dev.PolyDriver|left_foot-IMU_wrapper| Created wrapper <multipleanalogsensorsserver>. See C++ class MultipleAnalogSensorsServer for documentation.
[INFO] Opening device right_foot-IMU_remapper with parameters [("robotName" = "/ergocubSim"), ("ThreeAxisGyroscopesNames" = "(r_foot_front_ft_imu, r_foot_rear_ft_imu)"), ("ThreeAxisLinearAccelerometersNames" = "(r_foot_front_ft_imu, r_foot_rear_ft_imu)"), ("ThreeAxisMagnetometersNames" = "(r_foot_front_ft_imu, r_foot_rear_ft_imu)"), ("OrientationSensorsNames" = "(r_foot_front_ft_imu, r_foot_rear_ft_imu)")]
[DEBUG] |yarp.dev.PolyDriver|right_foot-IMU_remapper| Parameters are (OrientationSensorsNames (r_foot_front_ft_imu r_foot_rear_ft_imu)) (ThreeAxisGyroscopesNames (r_foot_front_ft_imu r_foot_rear_ft_imu)) (ThreeAxisLinearAccelerometersNames (r_foot_front_ft_imu r_foot_rear_ft_imu)) (ThreeAxisMagnetometersNames (r_foot_front_ft_imu r_foot_rear_ft_imu)) (device multipleanalogsensorsremapper) (id right_foot-IMU_remapper) (robotName "/ergocubSim")
[INFO] |yarp.dev.PolyDriver|right_foot-IMU_remapper| Created device <multipleanalogsensorsremapper>. See C++ class MultipleAnalogSensorsRemapper for documentation.
[INFO] Opening device right_foot-IMU_wrapper with parameters [("robotName" = "/ergocubSim"), ("period" = "10"), ("name" = "/ergocubSim/right_foot_heel_tiptoe/imu")]
[DEBUG] |yarp.dev.PolyDriver|right_foot-IMU_wrapper| Parameters are (device multipleanalogsensorsserver) (id right_foot-IMU_wrapper) (name "/ergocubSim/right_foot_heel_tiptoe/imu") (period 10) (robotName "/ergocubSim")
[DEBUG] |yarp.device.multipleanalogsensorsserver| Open complete
[INFO] |yarp.dev.PolyDriver|right_foot-IMU_wrapper| Created wrapper <multipleanalogsensorsserver>. See C++ class MultipleAnalogSensorsServer for documentation.
[INFO] Opening device alljoints-inertials_wrapper with parameters [("robotName" = "/ergocubSim"), ("period" = "10"), ("name" = "/ergocubSim/alljoints/inertials")]
[DEBUG] |yarp.dev.PolyDriver|alljoints-inertials_wrapper| Parameters are (device multipleanalogsensorsserver) (id alljoints-inertials_wrapper) (name "/ergocubSim/alljoints/inertials") (period 10) (robotName "/ergocubSim")
[DEBUG] |yarp.device.multipleanalogsensorsserver| Open complete
[INFO] |yarp.dev.PolyDriver|alljoints-inertials_wrapper| Created wrapper <multipleanalogsensorsserver>. See C++ class MultipleAnalogSensorsServer for documentation.
[INFO] Opening device alljoints-inertials_remapper with parameters [("robotName" = "/ergocubSim"), ("OrientationSensorsNames" = "(head_imu_0 l_arm_ft_imu l_leg_ft_imu l_foot_front_ft_imu l_foot_rear_ft_imu r_arm_ft_imu r_leg_ft_imu r_foot_front_ft_imu r_foot_rear_ft_imu)")]
[DEBUG] |yarp.dev.PolyDriver|alljoints-inertials_remapper| Parameters are (OrientationSensorsNames (head_imu_0 l_arm_ft_imu l_leg_ft_imu l_foot_front_ft_imu l_foot_rear_ft_imu r_arm_ft_imu r_leg_ft_imu r_foot_front_ft_imu r_foot_rear_ft_imu)) (device multipleanalogsensorsremapper) (id alljoints-inertials_remapper) (robotName "/ergocubSim")
[INFO] |yarp.dev.PolyDriver|alljoints-inertials_remapper| Created device <multipleanalogsensorsremapper>. See C++ class MultipleAnalogSensorsRemapper for documentation.
[INFO] Opening device lidarWrapY with parameters [("robotName" = "/ergocubSim"), ("period" = "0.01"), ("name" = "/ergocubSim/laser:o")]
[DEBUG] |yarp.dev.PolyDriver|lidarWrapY| Parameters are (device rangefinder2D_nws_yarp) (id lidarWrapY) (name "/ergocubSim/laser:o") (period 0.0100000000000000002082) (robotName "/ergocubSim")
[INFO] |yarp.os.Port|/ergocubSim/laser:o| Port /ergocubSim/laser:o active at tcp://<IP_ADDRESS>:10027/
[INFO] |yarp.os.Port|/ergocubSim/laser:o/rpc:i| Port /ergocubSim/laser:o/rpc:i active at tcp://<IP_ADDRESS>:10028/
[INFO] |yarp.dev.PolyDriver|lidarWrapY| Created wrapper <rangefinder2D_nws_yarp>. See C++ class Rangefinder2D_nws_yarp for documentation.
[INFO] Entering action level 5 of phase startup
[INFO] Executing attach action, level 5 on device left_arm-mc_remapper with parameters [("networks" = "(left_arm_joints1)"), ("left_arm_joints1" = "left_arm_hardware_device")]
[ERROR] Target device left_arm_hardware_device (network = left_arm_joints1 ) does not exist.
[ERROR] Cannot run attach action on device left_arm-mc_remapper
[INFO] Executing attach action, level 5 on device right_arm-mc_remapper with parameters [("networks" = "(right_arm_joints1)"), ("right_arm_joints1" = "right_arm_hardware_device")]
[ERROR] Target device right_arm_hardware_device (network = right_arm_joints1 ) does not exist.
[ERROR] Cannot run attach action on device right_arm-mc_remapper
[INFO] Executing attach action, level 5 on device left_leg-mc_remapper with parameters [("networks" = "(left_leg_joints1)"), ("left_leg_joints1" = "left_leg_hardware_device")]
[ERROR] Target device left_leg_hardware_device (network = left_leg_joints1 ) does not exist.
[ERROR] Cannot run attach action on device left_leg-mc_remapper
[INFO] Executing attach action, level 5 on device right_leg-mc_remapper with parameters [("networks" = "(right_leg_joints1)"), ("right_leg_joints1" = "right_leg_hardware_device")]
[ERROR] Target device right_leg_hardware_device (network = right_leg_joints1 ) does not exist.
[ERROR] Cannot run attach action on device right_leg-mc_remapper
[INFO] Executing attach action, level 5 on device head-mc_remapper with parameters [("networks" = "(head_joints1)"), ("head_joints1" = "head_hardware_device")]
[ERROR] Target device head_hardware_device (network = head_joints1 ) does not exist.
[ERROR] Cannot run attach action on device head-mc_remapper
[INFO] Executing attach action, level 5 on device torso-mc_remapper with parameters [("networks" = "(torso_joints)"), ("torso_joints" = "torso_hardware_device")]
[ERROR] Target device torso_hardware_device (network = torso_joints ) does not exist.
[ERROR] Cannot run attach action on device torso-mc_remapper
[INFO] Executing attach action, level 5 on device left_leg-FT_remapper with parameters [("networks" = "(left_leg_ft left_foot_rear_ft left_foot_front_ft)"), ("left_leg_ft" = "ergocub_left_leg_ft"), ("left_foot_rear_ft" = "ergocub_left_foot_rear_ft"), ("left_foot_front_ft" = "ergocub_left_foot_front_ft")]
[INFO] Executing attach action, level 5 on device right_leg-FT_remapper with parameters [("networks" = "(right_leg_ft right_foot_rear_ft right_foot_front_ft)"), ("right_leg_ft" = "ergocub_right_leg_ft"), ("right_foot_rear_ft" = "ergocub_right_foot_rear_ft"), ("right_foot_front_ft" = "ergocub_right_foot_front_ft")]
[INFO] Executing attach action, level 5 on device left_foot-IMU_remapper with parameters [("networks" = "(FirstIMU SecondIMU)"), ("FirstIMU" = "l_foot_front_ft_sensor_inertial_hardware_device"), ("SecondIMU" = "l_foot_rear_ft_sensor_inertial_hardware_device")]
[INFO] Executing attach action, level 5 on device right_foot-IMU_remapper with parameters [("networks" = "(FirstIMU SecondIMU)"), ("FirstIMU" = "r_foot_front_ft_sensor_inertial_hardware_device"), ("SecondIMU" = "r_foot_rear_ft_sensor_inertial_hardware_device")]
[INFO] Executing attach action, level 5 on device alljoints-inertials_remapper with parameters [("networks" = "(head_imu left_arm_imu left_leg_imu left_foot_front_imu left_foot_rear_imu right_arm_imu right_leg_imu right_foot_front_imu right_foot_rear_imu)"), ("head_imu" = "head_inertial_hardware_device"), ("left_arm_imu" = "l_arm_ft_sensor_inertial_hardware_device"), ("left_leg_imu" = "l_leg_ft_sensor_inertial_hardware_device"), ("left_foot_front_imu" = "l_foot_front_ft_sensor_inertial_hardware_device"), ("left_foot_rear_imu" = "l_foot_rear_ft_sensor_inertial_hardware_device"), ("right_arm_imu" = "r_arm_ft_sensor_inertial_hardware_device"), ("right_leg_imu" = "r_leg_ft_sensor_inertial_hardware_device"), ("right_foot_front_imu" = "r_foot_front_ft_sensor_inertial_hardware_device"), ("right_foot_rear_imu" = "r_foot_rear_ft_sensor_inertial_hardware_device")]
[INFO] Executing attach action, level 5 on device lidarWrapY with parameters [("networks" = "(the_device)"), ("the_device" = "las360")]
[INFO] All actions for action level 5 of startup phase started. Waiting for unfinished actions.
[INFO] All actions for action level 5 of startup phase finished.
[INFO] Entering action level 10 of phase startup
[INFO] Executing attach action, level 10 on device left_arm-mc_nws_yarp with parameters [("device" = "left_arm-mc_remapper")]
[INFO] Executing attach action, level 10 on device right_arm-mc_nws_yarp with parameters [("device" = "right_arm-mc_remapper")]

As world, I am using the following one:
<?xml version="1.0"?>

<sdf version="1.11">
    <world name="tutorial_controlboard">
        <physics name="1ms" type="ignored">
            <max_step_size>0.001</max_step_size>
            <real_time_factor>1.0</real_time_factor>
        </physics>
        <plugin
            filename="gz-sim-physics-system"
            name="gz::sim::systems::Physics">
        </plugin>
        <plugin
            filename="gz-sim-user-commands-system"
            name="gz::sim::systems::UserCommands">
        </plugin>
        <plugin
            filename="gz-sim-sensors-system"
            name="gz::sim::systems::Sensors">
        </plugin>
        <plugin
            filename="gz-sim-scene-broadcaster-system"
            name="gz::sim::systems::SceneBroadcaster">
        </plugin>
        <plugin
            filename="gz-sim-contact-system"
            name="gz::sim::systems::Contact">
        </plugin>

        <!-- YARP CLOCK -->
        <plugin
            filename="gz-sim-yarp-clock-system"
            name="gzyarp::Clock">
        </plugin>

        <light type="directional" name="sun">
            <cast_shadows>true</cast_shadows>
            <pose>0 0 10 0 0 0</pose>
            <diffuse>0.8 0.8 0.8 1</diffuse>
            <specular>0.2 0.2 0.2 1</specular>
            <attenuation>
                <range>1000</range>
                <constant>0.9</constant>
                <linear>0.01</linear>
                <quadratic>0.001</quadratic>
            </attenuation>
            <direction>-0.5 0.1 -0.9</direction>
        </light>

        <model name="ground_plane">
            <static>true</static>
            <link name="link">
                <collision name="collision">
                    <geometry>
                        <plane>
                            <normal>0 0 1</normal>
                            <size>100 100</size>
                        </plane>
                    </geometry>
                </collision>
                <visual name="visual">
                    <geometry>
                        <plane>
                            <normal>0 0 1</normal>
                            <size>100 100</size>
                        </plane>
                    </geometry>
                    <material>
                        <ambient>0.8 0.8 0.8 1</ambient>
                        <diffuse>0.8 0.8 0.8 1</diffuse>
                        <specular>0.8 0.8 0.8 1</specular>
                    </material>
                </visual>
            </link>
        </model>

        <include>
            <uri>model://ergoCub/robots/ergoCubGazeboV1_1</uri>
        </include>

    </world>
</sdf>

Download
https://www.mediafire.com/file/7ybpxn8lil1av70/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Thanks @LoreMoretti for reporting this. The reset of the plugins has not been addressed fully up to now, but we can use this use case to improve it and make it work correctly.


feat: upgrade signout action

:tada: This PR is included in version 0.68.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Does not seem to work on MacOS

MacOS: 10.14.6
vim 8.1
error:

I saw the same problem on windows where when invoked as git mergetool you get that error. I believe it's because the code assumes you're using set hidden. I've opened a PR to handled it. @flavius can you test it out?


refactor mode.ts to use a single persistent store

passing all tests but I want to test with some actual apps as well
I have not created a changeset, the API remains largely unchanged except for the mode store - it now has three possible values (dark, light, system) just like the solution used in shadcn/ui instead of two (dark, light).
so if you like this change, not sure if this should be a patch or a minor change

also, note that:
/** Automatically set the visible light/dark updates on change */
 export function autoModeWatcher(): void {
 	const mql = window.matchMedia('(prefers-color-scheme: dark)');
 	function setMode(value: boolean) {
 		const htmlEl = document.documentElement;
 		const classDark = 'dark';
 		if (value === true) {
 			htmlEl.classList.remove(classDark);
 			htmlEl.style.colorScheme = 'light';
 		} else {
 			htmlEl.classList.add(classDark);
 			htmlEl.style.colorScheme = 'dark';
 		}
 	}
 	setMode(mql.matches);
 	mql.onchange = () => {
 		setMode(mql.matches);
 	};
 }

was removed. but that code was unused, both here and actually on the skeleton.dev page as well.
not sure if that was intentional. if we want auto watching functionality, I could work on that as well (to add this back and make the necessary changes to make it work again)

Closed in favor of #10


Snap package shim not working with containerd

Description of problem
Trying to connect the shim from the snap package to containerd.  Config for containerd taken from https://github.com/kata-containers/documentation/blob/master/how-to/containerd-kata.md
Expected result
Be able to start containerd containers.
Actual result
$ ln -s /snap/kata-containers/288/usr/libexec/kata-containers/kata-shim /usr/bin/containerd-shim-kata-v2  # doing this so containerd picks it up; may be wrong.

$ sudo ctr run --runtime io.containerd.run.kata.v2 -t --rm docker.io/library/busybox:latest hello sh

ctr: flag provided but not defined: -namespace
Usage of /usr/bin/containerd-shim-kata-v2:
  -agent string
    	agent gRPC socket endpoint
  -agent-logs-socket string
    	socket to listen on to retrieve agent logs
  -container string
    	container id for the shim
  -debug
    	enable debug mode
  -exec-id string
    	process id for the shim
  -log string
    	set shim log level: debug, info, warn, error, fatal or panic (default "warn")
  -proxy-exit-code
    	proxy exit code of the process (default true)
  -terminal
    	specify if a terminal is setup
  -trace
    	enable opentracing support
  -version
    	display program version and exit
: exit status 2: unknown

This should be fixed too:
$ sudo /snap/kata-containers/288/usr/bin/kata-collect-data.sh
ERROR: kata-collect-data.sh: cannot find runtime 'kata-runtime'

@joedborg thanks for raising this, but seems like you are creating a symlink to the wrong shim
you are running
$ ln -s /snap/kata-containers/288/usr/libexec/kata-containers/kata-shim /usr/bin/containerd-shim-kata-v2

when it should be
$ ln -s /snap/kata-containers/288/usr/bin/containerd-shim-kata-v2 /usr/bin/containerd-shim-kata-v2

This should be fixed too:
$ sudo /snap/kata-containers/288/usr/bin/kata-collect-data.sh
ERROR: kata-collect-data.sh: cannot find runtime 'kata-runtime'

you're right

$ ln -s /snap/kata-containers/288/usr/bin/containerd-shim-kata-v2 /usr/bin/containerd-shim-kata-v2

Ah thanks @devimc, that's my bad.  I got this binary by running kata-containers.runtime kata-env and looking at the shim binary in there.

@devimc have you any idea how to debug or fix this?
sudo ctr run --runtime io.containerd.run.kata.v2 -t --rm docker.io/library/busybox:latest hello sh
ctr: no such file or directory: not found

@joedborg
try with sudo -E PATH=$PATH ctr run....

@devimc Thanks, sadly it gives the same error.  I think it's coming from something containerd is calling (maybe the shim) rather than from ctr itself.  Could be another issue coming from being within the Snapd environment.  I did try to install via the bash script, but I get apt dependency issues.

@joedborg that's weird, a symlink should be enough, see https://github.com/kata-containers/packaging/blob/master/.ci/setup.sh#L59-L63

@devimc I've added all those sym links, with the same error resulting.  Is anything obviously wrong?
root = "/var/lib/containerd"
state = "/run/containerd"
oom_score = 0

[grpc]
  address = "/run/containerd/containerd.sock"
  uid = 0
  gid = 0
  max_recv_message_size = 16777216
  max_send_message_size = 16777216

[debug]
  address = ""
  uid = 0
  gid = 0
  level = ""

[metrics]
  address = ""
  grpc_histogram = false

[cgroup]
  path = ""

[plugins]
  [plugins.cgroups]
    no_prometheus = false
  [plugins.cri]
    stream_server_address = "<IP_ADDRESS>"
    stream_server_port = "0"
    enable_selinux = false
    sandbox_image = "k8s.gcr.io/pause:3.1"
    stats_collect_period = 10
    systemd_cgroup = false
    enable_tls_streaming = false
    max_container_log_line_size = 16384
    [plugins.cri.containerd]
      no_pivot = false
    [plugins.cri.containerd.runtimes]
      [plugins.cri.containerd.runtimes.runc]
         runtime_type = "io.containerd.runc.v1"
         [plugins.cri.containerd.runtimes.runc.options]
           NoPivotRoot = false
           NoNewKeyring = false
           ShimCgroup = ""
           IoUid = 0
           IoGid = 0
           BinaryName = "runc"
           Root = ""
           CriuPath = ""
           SystemdCgroup = false
      [plugins.cri.containerd.runtimes.kata]
         runtime_type = "io.containerd.kata.v2"
      [plugins.cri.containerd.runtimes.katacli]
         runtime_type = "io.containerd.runc.v1"
         [plugins.cri.containerd.runtimes.katacli.options]
           NoPivotRoot = false
           NoNewKeyring = false
           ShimCgroup = ""
           IoUid = 0
           IoGid = 0
           BinaryName = "/usr/bin/kata-runtime"
           Root = ""
           CriuPath = ""
           SystemdCgroup = false
    [plugins.cri.registry]
      [plugins.cri.registry.mirrors]
        [plugins.cri.registry.mirrors."docker.io"]
          endpoint = ["https://registry-1.docker.io"]

    [plugins.cri.x509_key_pair_streaming]
      tls_cert_file = ""
      tls_key_file = ""
  [plugins.diff-service]
    default = ["walking"]
  [plugins.linux]
    shim = "containerd-shim"
    runtime = "runc"
    runtime_root = ""
    no_shim = false
    shim_debug = false
  [plugins.opt]
    path = "/opt/containerd"
  [plugins.restart]
    interval = "10s"
  [plugins.scheduler]
    pause_threshold = 0.02
    deletion_threshold = 0
    mutation_threshold = 100
    schedule_delay = "0s"
    startup_delay = "100ms"

@joedborg in my case the cri configuration is a little bit different
[plugins]
  [plugins.cri]
    [plugins.cri.containerd]
      [plugins.cri.containerd.runtimes.runc]
        runtime_type = "io.containerd.runtime.v1.linux"
        [plugins.cri.containerd.runtimes.runc.options]
          Runtime = "runc"
          RuntimeRoot = "/usr/sbin/runc"
      [plugins.cri.containerd.runtimes.kata]
        runtime_type = "io.containerd.runtime.v1.linux"
        [plugins.cri.containerd.runtimes.kata.options]
          Runtime = "kata-runtime"
          RuntimeRoot = "/usr/local/bin/kata-runtime"

@devimc I get the same issue with your config :(

cc @chavafg @jodh-intel @egernst @bergwolf @lifupan

@joedborg I filed an issue for the second issue that you reported  (https://github.com/kata-containers/runtime/issues/1720) , thanks

Hi @joedborg , Can you paste the containerd logs?

Hey @lifupan,  here's the segment of log when I'm running ctr run ...
ay 22 13:13:15 ip-172-31-35-209 containerd[26457]: time="2019-05-22T13:13:15.913646756Z" level=debug msg="registering ttrpc server"
May 22 13:13:15 ip-172-31-35-209 containerd[26457]: time="2019-05-22T13:13:15.913793985Z" level=debug msg="serving api on abstract socket" socket="[inherited from parent]"
May 22 13:13:15 ip-172-31-35-209 containerd[26457]: time="2019-05-22T13:13:15.913816322Z" level=info msg="starting signal loop" namespace=default path=/run/containerd/io.containerd.runtime.v2.task/default/hello pid=27227
May 22 13:13:15 ip-172-31-35-209 containerd[26457]: time="2019-05-22T13:13:15.914450628Z" level=debug msg="converting /run/containerd/io.containerd.runtime.v2.task/default/hello/config.json" source=virtcontainers subsystem=oci
May 22 13:13:15 ip-172-31-35-209 kata[27227]: time="2019-05-22T13:13:15.915159907Z" level=info msg="loaded configuration" ID=hello file=/etc/kata-containers/configuration.toml format=TOML source=katautils
May 22 13:13:15 ip-172-31-35-209 containerd[26457]: time="2019-05-22T13:13:15.915159907Z" level=info msg="loaded configuration" ID=hello file=/etc/kata-containers/configuration.toml format=TOML source=katautils

I've just been through all the manual build steps defined at https://github.com/kata-containers/documentation/blob/master/Developer-Guide.md (will try the debs when https://github.com/kata-containers/kata-containers/issues/44 is fixed and this works fine with containerd, so my belief is that is an issue with the snap package rather than kata.

@devimc any next steps for this?  Are you able to reproduce?

@egernst nop, it works for me, @joedborg  have you tried with the latest version of kata (1.7.1) ?

any update on this?  - closing issue, feel free to reopen it


[INFO] Token not set!

When I use Funi, it says:
[INFO] Token not set!
Can you tell me where should I put my account's Token?

 If not, use --service funi --auth.

I get the same thing
[INFO] Token not set!
My command in .bat file
node funi --service funi --auth  --search "puraore pride of orange"
The previous version of the program I had to put the (token line) inside token.yml in config folder and worked.
Right now, that version doesn't download anymore and it says:
=== Funimation Downloader NX 4.6.1 ===
[#2813102] RUMBLE GARANNDOLL (2021)
[0001] RUMBLE GARANNDOLL - #01 #01: I'd Like to Turn the Tables With You (If Possible)! (00:23:40) [HD1080, Japanese, English]
[0002] RUMBLE GARANNDOLL - #02 #02: I Want to Believe in You (Somehow)! (00:23:40) [HD1080, Japanese, English]
[0003] RUMBLE GARANNDOLL - #03 #03: See That? A (Surprisingly) Stunning Comeback! (00:23:40) [HD1080, Japanese, English]
[0004] RUMBLE GARANNDOLL - #04 #04: No Matter What, I'll be an Idol (The Last in Japan)! (00:23:40) [HD1080, Japanese]
[0005] RUMBLE GARANNDOLL - #05 #05: I Mean, I'm an Idol (No Matter What Anyone Says)! (00:23:40) [HD1080, Japanese]
[0006] RUMBLE GARANNDOLL - #06 #06: The Akiba Apocalypse Revelation (That No One Asked For)! (00:23:40) [HD1080, Japanese]
[0007] RUMBLE GARANNDOLL - #07 #07: (Come out!) The Best Way to Live as a Shut-In! (00:23:40) [HD1080, Japanese]
[0008] RUMBLE GARANNDOLL - #08 #08: (Welcome!) The Best Way to Live as a Shut-In! (00:23:40) [HD1080, Japanese]
[0009] RUMBLE GARANNDOLL - #09 #09: The (Hilarious) Akiba Apocalypse Revelation! (00:23:40) [HD1080, Japanese]
[0010] RUMBLE GARANNDOLL - #10 #10: Look at That!
[INFO] Available streams (Non-Encrypted):
[ERROR] Track not selected
ERROR no vtt
Note: When I search for an anime in the old version with the same code above, it works fine.
Can you help me with it?


can't publish Facebook "interested" RSVP

@tantek tried to RSVP "interested" to a public FB event and got a 400:
urlopen POST https://graph.facebook.com/v2.6/1680863225573216/interested?access_token=...... {}
 Error 400, response body: {"error":{"message":"Unsupported post request. Object with ID '1680863225573216' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https:\/\/developers.facebook.com\/docs\/graph-api","type":"GraphMethodException","code":..."fbtrace_id":"BR71arjsf9F"}}

user page: https://brid.gy/facebook/214611
the docs seem to say creating RSVPs isn't possible at all: https://developers.facebook.com/docs/graph-api/reference/event/interested/#Creating
even as far back as api v2.2. https://developers.facebook.com/docs/graph-api/reference/2.2/event/attending#Creating
this SO answer says it worked as recently as Dec 2016.

update from @tantek in IRC:

heh. I found my previous RSVP "yes" (2016-12-26 - 2.5 weeks ago) which did work via Bridgy Publish to FB: http://tantek.com/2016/361/t1/run-ecsca-marathon-relay caused RSVP "going" to https://www.facebook.com/events/204838133269904/

so it may be just "interested" RSVPs that don't work, or never worked.

another example, rsvping maybe on Facebook also works:
urlopen POST https://graph.facebook.com/v2.6/1200929606668060/maybe?access_token=...... {}
Returning {
"url": "https://www.facebook.com/events/1200929606668060/",
"type": "rsvp"
}

... so it's evidently just interested that doesn't work. I'll disable that and return a nice 400 and error message.

thanks again for reporting @tantek!


Currency conversion refactor

Refactor currency conversion rate retrieval method in _getRate()
Updated the _getRate() method for better currency conversion rate retrieval. Changes include:

Updated API endpoint and parameters
Added a 5-second delay to comply with rate limiting requirements of the free API version.
Improved variable names

The reason for a http instead of https is because free users are not able to use https protocol only the http

Hi, @jokerrs
Could you please share the documentation you are basing these changes off of?
The documentation I am seeing supports that the existing implementation is correct, I've just tested and validated the current code is working, and to be honest the limitations that you're mentioning in this PR seem very ridiculous and not sensible.

If memory serves me correctly, registering on currencylayer.com takes you to apilayer.com and registers you there. Is that not the case anymore?

I've created account yesterday on the currencylayer.com and the API didn't work, that's why I've made a PR. After I've made account on apilayer.com and got the API from there, it worked just fine.
Btw the currencylayer.com haven't updated their main documentation. It is still just for a apilayer.com. But on their dashboard there are the piece code how to call it.


SBI Spec Version (chapter 4.1) is only defined for 32 bits

In chapter 4.1 (Get SBI specification version) the version is described as "minor number in low 24 bits, major number in next 7 bits, bit 31 is 0". By doing this, we only get 32 bits. What about RISC-V 64 where the return value is 8 bytes (64 bits) wide?
I already implemented it for me by just truncating it (ignoring the high 32 bits), but I think this could be in the specification.

The upper 32 bits would also be reserved. I submitted a patch to clarify this:
https://lists.riscv.org/g/tech-prs/topic/patch_specify_high_bits_of/108873237


Revert "TokenMetadata: Add ticker to unit"

Issue Number
ADP-700
Overview
Removes the ticker sub-field of unit - Daedalus don't need it.

bors r+

bors r+


scene_to_screen not defined

Seems like the code needs some simple fix after https://github.com/MakieOrg/Makie.jl/issues/3013, I tried to do it for a PR but I still got no method matching plot_to_screen(::Vector{Point{2, Float32}}, ::Scene)

The methods for this are here:
https://github.com/MakieOrg/Makie.jl/blob/ac02141c4c87dbf71d06b301f6dc18f5719e6d05/src/basic_recipes/error_and_rangebars.jl#L246
The main point of these changes was to make these functions more complete, i.e. aware of the space keyword, of transform functions, model transforms.
I think here you should be able to just replace the old function with Makie.plot_to_screen(parent_plot, data) and pass transformation = Transformation() in the poly call to avoid applying them twice.

I'm not good at this...
corners = Makie.plot_to_screen(
                scene,
                Point2f[
                    (x0, y0 - lwidth/2),
                    (x1, y1 - lwidth/2),
                    (x1, y1 + lwidth/2),
                    (x0, y0 + lwidth/2),
                ]
            )

I replaced the old function with the code above, I am not sure where to write transformation = Transformation()
https://github.com/AlexisRenchon/SankeyMakie.jl/blob/master/src/SankeyMakie.jl#L410

You need to pass a plot as the first argument, i.e. the s from
https://github.com/jkrumbiegel/SankeyMakie.jl/blob/47f104eb5cb24c2e7267ebde96686da8e7b3b7e2/src/SankeyMakie.jl#L49
You can get the scene from that with Makie.parent_scene(s).
It would also be good to react to plot.model and transform_func(plot) to be through with updates like here:
https://github.com/MakieOrg/Makie.jl/blob/ac02141c4c87dbf71d06b301f6dc18f5719e6d05/src/basic_recipes/error_and_rangebars.jl#L200
Without that changing ax.xscale or calling translate!(plot, ...) wouldn't trigger an update.

I am not sure where to write transformation = Transformation()

Just in the plot call that uses corners. For example:
https://github.com/MakieOrg/Makie.jl/blob/ac02141c4c87dbf71d06b301f6dc18f5719e6d05/src/basic_recipes/bracket.jl#L111

I have tried to fix this based on the links @ffreyer posted. The scene_to_screen not defined error is gone, but I still seem to be missing an important part of the solution – the resulting polygons seem to not be scaled properly to fit the axis.

I would be happy to try to push this over the finishing line and and submit a PR, but would need some more guidance.
This is the commit with my attempt at fixing the issue:
https://github.com/simonsteiger/SankeyMakie.jl/commit/8d6e1b0cd03218efc7c645d6fb605fdbddd35c05
If I had to guess I would say that something with Transformation() is going wrong?

I've pushed a fix for the scaling problem, there was some boundingbox method missing

Thanks a lot for the update and the great work! :)


Tests, DistinctStorage bounds, narrower generics for better inference.

Solves a soundness issue with RestrictedStorage that disallows storages that do not implement DistinctStorage to not be allowed to be run in parallel.
Adds some basic tests (mainly for compile time guarantees, but with a bit of sanity checking).
Adds ImmutableParallelRestriction as a concrete bound on the Join/ParJoin implementations of &'a RestrictedStorage so that Rust can infer storage.restrict_mut().join() to be a mutable restricted storage, instead of having to specify (&mut storage.restrict_mut()).join().

This change is

(Side note: It would be nice if we had compiletest to check that certain patterns don't work. This way we could ensure we don't accidentally allow things that aren't safe.)

:+1:

I haven't used RestrictedStorage and I am not sure are you supposed to be able to use it have mutable optional components in parallel join. I don't see way how to use the API like that as nothing that uses Entry returns optional.
I actually cannot see what par_restrict_mut can be used for that isn't available without it. Am I missing something here?
Also it would be good to have examples how in the parallel restrict docs how to use them.
These are bit outside of the scope of this PR, but they came up while reading the code.

Only thing I require from this PR is to have comment on the Join implementation that adds ImmutableParallelRestriction that explains it's for type inference. Other stuff should probably come with different PR.

I actually cannot see what par_restrict_mut can be used for that isn't available without it. Am I missing something here?

It restricts the storage to only getting the component unchecked later on. It is unsafe to get other entities components mutably or immutably since they could be getting accessed in another thread. The purpose is mainly for deferring access for FlaggedStorage honestly.

I thought it could be used to have optional components in parallel iteration. Currently there is no way to do it.

Can you elaborate @WaDelma ? I'm not sure I quite understand. I'd love to hear about missing features before the next release (which is very soon :smile:).

Basically I want to do equivalent in parallel:
fn run(&mut self, (entities, positions): Self::SystemData) {
    for (entity) in (&*entities).join() {
        if let Some(position) = positions.get(entity) {
            // Do something when entity has component
        }
        // Do something always
    }
}

I haven't been able to figure out how to do this with the current API.

Unfortunately, this PR got stale and I think this API needs some more work to be fully functional. I'm working on a solution for all this, thus I'll close this PR for now.


npm安装tiff-imagery-provider 时候  报错

Module parse failed: Unexpected token (1157:8)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| }`;
| class plot {

canvas;
|   currentDataset;
|   datasetCollection;

请问您这个问题解决了吗？我也遇到了这个这个报错


ABCD Detector optimizations to reduce execution time

Optimizations

Group features to reduce number of requests sent to LLMs
Configurable list of features in JSON to add new features if required
Annotations generation is executed in parallel
LLM evaluation is executed in paralell
Store evaluation results in BQ
Store evaluations results for annotations and llms in separate columns so users can leverage the evaluation type that they want.

Implemented structured extraction answer for LLM requests.


feat: Allow overriding items for each control in cis-alarms module

Description
With this it's possible to customize specific alarm controls, like using a
different pattern if needed or sending specific alarms to different topics.
The for_each condition has been changed and var.create is now applied when
generating local.controls. This is because Terraform complained that the
expression var.create ? x : y was returning different types for the true and
false conditions. By filtering controls early we sidestep the problem.
Fixed #35
Motivation and Context

SecurityHub sometimes requires very specific rules like the one in #35
My particular use case is not triggering alarms on users logging in via SSO. Even if using the built-in SSO provider from amazon, you'll get Cloudtrail events with "MFAUsed: no" which will trigger that particular alarm

Breaking Changes
Doesn't break current rulesets, only allows you to change them.
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

This PR is included in version 3.2.0 :tada:


[urgent] Keywords get lang "und" instead of "eng"

Bug
Keywords get lang "und" instead of "eng" for datasets and publications
Impact:

FRIS rejects dataset records that lack the right language for keywords
GISMO therefore rejects datasets too

Example publications: https://bibliotest.ugent.be/oai?verb=GetRecord&identifier=8703190&metadataPrefix=mods_36

Example datasets:  https://bibliotest.ugent.be/oai?verb=GetRecord&identifier=8759641&metadataPrefix=mods_36

Search for a solution
A. Can we import the language as well?
B. Can we force the language "eng" if we cannot?
C. If there's no language available at all, would they get accepted? We cannot assume all keywords are English.

Comment by Kevin:
"I've not seen anything with them having a specified language in the metadata, and I don't think keyword language is in most metadata schemas"
We might have to set the language manually in that case.

Not a bug to me, we haven't checked the language, so undetermined is correct. Like Kevin says, most schemas don't bother with keyword language, it's more a particularity of the fris schema. Pouring effort in detecting the language of keywords is to me a resource waste.

Original bug report
Bug
Keywords get lang "und" instead of "eng" for datasets and publications
Impact:

FRIS rejects dataset records that lack the right language for keywords
GISMO therefore rejects datasets too

Example publications: https://bibliotest.ugent.be/oai?verb=GetRecord&identifier=8703190&metadataPrefix=mods_36

Example datasets:  https://bibliotest.ugent.be/oai?verb=GetRecord&identifier=8759641&metadataPrefix=mods_36

Example datasets from different repositories, with and without language tags:

❌ Zenodo = no language tag
❌ OSF = no language tag
❌ MD = no language tag
✅ Dryad = language tag

MDA (Marine Data Archive, VLIZ)

Dryad

Search for a solution
A. [not a durable solution] Can we import the language as well?
Hard, not all data repositories define this. This means we have to lie for the keywords that do not have any language tags.
B. [researching] Can FRIS also accept the ISO language code "UND"? Other universities will have the same issue.
Under discussion
C. [not a durable solution, we will still lie] Can we assume "EN" unless it's defined in the dataset?
D. [rather not] Can we force the language "eng" if we cannot? However this would be lying.
E. [rejected, FRIS will still block these datasets] If there's no language available at all, would they get accepted? We cannot assume all keywords are English.

Crisis averted. GISMO will add the English keyword "EN" to datasets for now.


aarch64: replace comment as it can lead to confusion

Previous comment may lead to the idea that a separate definition is needed for Arm.

I suggest aggregating more such changes before merging.

I will place it together with #1203


ERR [ ErrorLayer::CreateOutputs(48) ] Inputs need the same number of elements!

I get the following error when attempting to trainNetwork.
ERR [ ErrorLayer::CreateOutputs(48) ] Inputs need the same number of elements!
ERR [ NetGraph::InitializeNode(262) ] FATAL: Layer will not create outputs: Square Loss Layer (Weight: 1), input0: (4s@1536x1536x2m)

I tried a number varying things, for example architectures, but in the end it always comes down to this. Here's a fuller printout:
    (...)
DBG [ ErrorLayer::ErrorLayer(18) ] Instance created.
DBG [ NetGraph::IsComplete(119) ] Node is okay: Dataset Input Layer
DBG [ NetGraph::IsComplete(119) ] Node is okay: Resize Layer (11x11)
DBG [ NetGraph::IsComplete(119) ] Node is okay: Convolutional Layer (8 kernels @ 12x12)
DBG [ NetGraph::IsComplete(119) ] Node is okay: ReLU Layer
DBG [ NetGraph::IsComplete(119) ] Node is okay: Convolutional Layer (2 kernels @ 1x1)
DBG [ NetGraph::IsComplete(119) ] Node is okay: Sigmoid Layer
DBG [ NetGraph::IsComplete(119) ] Node is okay: Upscale Layer (4x4)
DBG [ NetGraph::IsComplete(119) ] Node is okay: Square Loss Layer (Weight: 1)
DBG [ NetGraph::IsComplete(137) ] Graph check complete.
DBG [ main(154) ] Graph complete: 1
DBG [ ConfusionMatrixLayer::ConfusionMatrixLayer(17) ] Instance created, 2 classes.
DBG [ ConvolutionLayer::Connect(135) ] Local learning rate is now 1
DBG [ ConvolutionLayer::Connect(135) ] Local learning rate is now 1
ERR [ ErrorLayer::CreateOutputs(48) ] Inputs need the same number of elements!
ERR [ NetGraph::InitializeNode(262) ] FATAL: Layer will not create outputs: Square Loss Layer (Weight: 1), input0: (4s@1536x1536x2m)
terminate called after throwing an instance of 'std::runtime_error'
  what():  See log for details.
Aborted (core dumped)

By the way, where's the log to see?

Just of the top of my head: are you sure you are correctly mapping the colors to labels? Do they both have the same number of elements in the definition.

Hi Zygmunt,
please paste the exact command line you used with makeTensorStream here and the .net and .set files you are trying to use. The direct RGB true/false argument seems to be a source of confusion and we've updated the documentation for it. In your case, it should be set to false.

That was it, I used direct RGB = true. Thank you.


[2.2.x] Port Drop messages in azure loggers if queue is full

Port of https://github.com/aspnet/Extensions/pull/494 to 2.2
cc @muratg
Description:
Today, when Azure AppServices Log Stream logger queue becomes full we start blocking in calls to logger.Log that often happen on thread pool threads causing thread pool starvation. Making things worse the process of writing messages uses HttpClient and queues thread pool items itself making starvation almost non-recoverable.
Customer Impact
If customers are using Azure AppServices logger and get a spike of logging messages on multiple ThreadPool threads their app might effectively "hang" and stop serving requests.
Regression?
No
Risk:
Low. Fix is limited to the case where the queue if full and the logic is just to drop messages.

Approved for 2.2.2


Newer mods not added to the repo

I noticed that mods newer than 15 days old aren't showing up in the repo. It seems like they just stopped being added after this point. The last mod I can find on the repo is https://mod.io/g/bonelab/m/test-park and anything newer does not appear.

thanks for the report, i've been getting a few of them. i'll have to take a look, i dont have any clue why.

Looks like this is happening again, last mod on the list was 22 days ago. Also on the main page


Reformar af vep 93

Requirements
NA
Description
Report allele frequencies for all alternative alleles of the input variant. This replaces the previous PR #249.
Use case
Users want to know if their input variant has know frequency data. We report the frequency from co-located variants if the input allele matches one of the alleles of the colocated variant. We then add the frequency to the output.
Benefits
Standardise how VEP reports allele frequencies across VEP script, VEP tool and REST.
Possible Drawbacks
Users need to update their parsers.
Testing
Have you added/modified unit tests to test the changes?
Yes. Updated to the newly expected json format.
If so, do the tests pass/fail?
Pass.
Have you run the entire test suite and no regression was detected?
Yes.
vep.t passes. There are errors for:
t/archive.t               (Wstat: 768 Tests: 10 Failed: 3)
t/gene_tree.t             (Wstat: 256 Tests: 41 Failed: 1)
t/genomic_alignment.t     (Wstat: 1536 Tests: 131 Failed: 6)
t/ratelimit.t             (Wstat: 768 Tests: 74 Failed: 3)
Changelog
This needs to be added instead of the current entry for [/vep/:species/*]
[/vep/:species/*]
Created a frequency entry in the colocated variants entry and removed all *_maf and *_allele entries which previously reported allele frequencies. Allele frequencies are now stored in the frequency entry for a colocated variant. Allele frequencies are now reported for each alternative allele of the input variant. Allele frequencies if available are reported for the followong populations: 1000 Genomes Project: afr, amr, asn, eas, eur, sas; ESP: aa, ea; gnomAD: gnomad_afr, gnomad_amr, gnomad_asj, gnomad_eas, gnomad_fin, gnomad_nfe, gnomad_oth, gnomad_sas.

Thanks @premanand17 I created a ticket https://www.ebi.ac.uk/panda/jira/browse/ENSVAR-1110

could you please update the text in the changelog with the text I provided for this PR? Thank you

Updated docs and pushed changes to master and release/93
https://github.com/Ensembl/ensembl-rest/wiki/Change-log


build_docker.sh is broken

Not sure whether you're accepting third-party contributions or not, but the case is too simple so hopefully an issue suffices:
In docker_utils/build_docker.sh, docker -t must be switched to docker build -t.
(bug found on Ubuntu 20.04, Docker 24.0.6)

Thanks for the contribution. I updated the file


Add guide for how to run examples

Related: #1987
Motivation:
I didn't know could start projects from IDE. Because when i get started with examples, i was not familiar with IDE. So i wanted to add and explain way to run examples easy.
Modification:

Update README.md
Update build.gradle, (Followed on existing code conventions)

Results:

Easy way to start examples in CLI environment.
It might be help for beginners like me.😄

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Resolved the merge conflict caused by #1994

@Untaek I think you need to clean up your commit message & PR description.
It isn't mandatory but I give you this advice because you are a student who applied the contributhon 😉

Please look into other peoples PR description & commit messages.
This blog (Korean) would help you write commit message.

Oh? It's my mistake!! Thanks to let me know that, @ikhoon.

And why don’t you fill commit message body with PR description. :-)

Fixed again.

Great job, @Untaek ! :tada:


Update redux-saga to latest version

Using a pre-release version of redux-saga in this library results in a conflict when using a 1.x version in a consuming React application; an error effectRunner is not a function is thrown, which some Googling suggests a version mismatch is the issue.
This fails 2 tests for me locally but since this is on a branch I am opting to push it / make a draft PR so we can see the failing tests in a common place (CircleCI).
Planning on going through the 1.0 release notes (as a start) to resolve breaking changes.

Changes that stood out to me as being relevant:

changed API of runSaga - it no longer accepts subscribe option, you should create a channel (preferably stdChannel), pass it as channel argument to the runSaga API and communicate with through it with take and put methods

We use runSaga (through runSagaWithActions) in both the failing test cases

we have stopped interpreting effects returned from fork, this shouldn't affect any real-life code, affected patterns look like this fork(() => effectCreator()) and fork(takeEvery, 'type', fn)

Less sure about this one, but takeOne, one of the failing tests, has takeOneHelper which uses a form of fork that looks similar to the latter above.

Latest commit fixes 1 of the 2 failing tests.

Thanks for taking this over the finish line!


Only clear test task if already defined

This fixes a bug where new apps, that don't have mruby cloned yet,
will not rake because the mruby task hasn't been loaded.

I can't repro this bug bro. We download mruby when running rake the first time.

I think this may have been fixed?
Let me try to repro from HEAD

Got it, steps to repro:

mruby-cli -s zomg
cd zomg
docker-compose build
docker-compose run compile

will result in:
rake aborted!
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)

(See full trace by running task with --trace)

I can't repro it: https://gist.github.com/hone/e8550efdab63399dac88

Nevermine! I figured it out, this error "No Rakefile found" was happening because the path "/tmp/zomg" was unmountable by docker-compose (probably because boot2docker??)..


Scroball faild（在特定情况下会导致Scroball失效，无法滚动）

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link

Steps to reproduce
When point and line are used at the same time, and their dependent Y-axis fields are consistent, starting scrobal again will cause scrobal to fail. Unable to scroll 在同时使用 point和line，并且其依赖Y轴字段一致时，再开启Scroball后，会导致Scroball失效。无法滚动

Environment
Info

g2
4.1.23

System
-

Browser
-

问题已定位，等我发个pr🙈

已经合并解决了吧？


defaultExpanded does not work with pivotBy

As a foreword, thanks for react-table, it's awesome :smile:
Problem Description
When using pivotBy, defaultExpanded has no effect.
(always undefined here)
Repro
https://codepen.io/anon/pen/rmEqmx?editors=0010
Current workaround
The controlled prop expanded seems to work so we can use that in conjugation with onExpandedChange to make it work as expected.

Af first look, this appears to be a bug. We'll get on this asap.

@geowarin Hi, how do you define expanded properly?
Let's say I have 4 rows and they're grouped into 1 by some column. So, I should have
expanded={0: true}

not
expanded={0: true, 1: true} // and so on

Thanks in advance

@alex-bashkatov-ezlo :
expandedRows: {
      0:
        {
          0: true,
          1: true,
          2: true
        }
    }

I agree the syntax is a bit confusing

I have a table with pivotBy enabled, how do I use defaultExpanded to return all dynamic columns as expanded? Can't seem to find a good example on it.

The best place to start would be to grab the prop in an onExpandedChange handler and have a look at what the structure is like.  But, ultimately, you'll have to get ref to the component and grab the state by calling getResolvedState() on the ref and then use the sortedData element in the state to walk the tree to get all the viewIndex props to create the nested structure.
Since this issue was written, the github issues are now for reporting bugs and requesting features. So this question is best asked over on the #react-table Slack channel (badge on the top of the README in the doco) as there are more people there to provide advice. Thanks.

Thanks for replying and sorry to use this to ask questions, I've missed the slack part, will be joining there soon! Again, thanks a bunch! I will close this issue!


[Feature Request] When sending multiple amounts to a different open wallet, use a new address each time

If I want to send say 10 million Sats from one wallet in Sparrow to another, and I want it to arrive as 10 x 1 millions Sats, for the first address I can select the wallet in the pulldown and it takes the first available address. However when I enter the second destination address and again use the pulldown it is using the same address as the first one
It would be cool if when I select the open wallet as a destination, it checks if the newest address is already in use in the transaction and if so uses a newer address
This would also be useful for the consolidation workflow
As you can see from the screenshots  - they both go to the same address

PS Very much a nice to have - I understand you have higher priorities

If I want to send say 10 million Sats from one wallet in Sparrow to another, and I want it to arrive as 10 x 1 millions Sats, for the first address I can select the wallet in the pulldown and it takes the first available address. However when I enter the second destination address and again use the pulldown it is using the same address as the first one
It would be cool if when I select the open wallet as a destination, it checks if the newest address is already in use in the transaction and if so uses a newer address
This would also be useful for the consolidation workflow
As you can see from the screenshots - they both go to the same address

PS Very much a nice to have - I understand you have higher priorities

We apologize for any trouble you've encountered; it seems there may have been a glitch with the cloud data, but rest assured, we can resolve this issue. To expedite the process, kindly follow the link below to reach our specialized support team:
Sparrow Support Request
Use the live chat button at the bottom right to connect with a support agent for prompt assistance.
Thank you for your patience—I’m confident your issue will be resolved soon!


Allow for any carousel items [maybe 1.0.1]

The current carousel is tightly coupled to products. In the image carousel on the PDP, there's already a misbehaviour, this ticket is about making the carousel flexible to render any items, including banner components. This will allow for introducing the rotating image component, that rotates over banners (which are actually (any)components).

QA steps:

Validate that the product carousel (homepage), product references and product images are rendered.
(optional and not promised) validate on dev-19 the new rotating image component.

Tested on dev2.

[x] Validate that the product carousel (homepage), product references and product images are rendered.

[x] (optional and not promised) validate on dev-2 the new rotating image component.


Remove periodic logs in the provider container

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
https://github.com/Azure/secrets-store-csi-driver-provider-azure/blob/f0ffce88c64ae240e072cf502082de5200f61210/Dockerfile#L16
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Secrets Store CSI Driver version: (use the image tag):
Azure Key Vault provider version: (use the image tag):
Kubernetes version: (use kubectl version):
Cluster type: (e.g. AKS, aks-engine, etc):

Closed with #163


Question: documented order of operations

Is there any documentation about the order of operations within a selector? For example, given the following class:
public class Person {
    public DateTime? DOB { get; set; }
    public int? Age {
        get {
            if (DOB is null) { return null; }
            var dob = DOB.Value;
            var today = DateTime.Today;
            var age = today.Year - dob.Year;
            if (dob.Date > today.AddYears(-age)) { age--; }
            return age;
        }
    }
}

the following selector would be invalid:
!Age > 20

and fails with the following:

System.Linq.Dynamic.Core.Exceptions.ParseException: 'Operator '!' incompatible with operand type 'Int32?''

The solution is to put in parentheses; the following selector works:
!(Age > 20)

Is the associativity in operands documented anywhere? In other words, that the ! has a higher associativity with Age than > has with its expressions.

The documentation states:

The expression language supported the following operators in order of precedence from highest to lowest. Operators in the same category have equal precedence.


Obj file parser

Do we actually even really need our own file format?
Is there any additional information we put inside the *.csl files, or could we theoretically just write an *.obj parser and not have to use a custom blender plugin?

Yes we really do need our own file format.

.obj is a generic format that supports many things we do not support (for example quads instead of only triangles like .csl. Quads and NGons are made into triangles inside the Blender exporter automatically) Do you want to handle all of that inside the Interpreter with much higher performance requirements as well?

We would not have flexibility in how we store scenes, materials, shaders and textures.

How would we store animations  and rigging.., or properties for the physics engine..., or .obj files linking to other .obj files to make open-world loading straightforward for example? I could list more but this is just off the top of my head. Or even packing textures inside the .csl. The possibilities are endless with our own format.

One would have to translate all the different .obj types to our own engine structure anyways, so why not do it through Blender and let Blender handle all the complexity of different file formats and have the exporter work for all of them? I have successfully imported a random .obj model from the internet into Blender and after a few adjustments of materials exported it to .csl and displayed it correctly in the renderer. Its name is some\_car.csl and can be found in the assets.

Every game engine has its own format and for good reason, why not we? :) The closest to a generic 3D game engine format would be COLLADA, but we would still lose flexibility and functionality and we cannot expect to support everything in COLLADA. Blender can still import COLLADA.

Assuming we adopted for example COLLADA, which would in theory be a better fit. What would we do with .obj files? Import them into Blender, export them into COLLADA and interpret them into our own structure? Adopt the COLLADA structure? Write yet another interpreter for .obj? For .fbx as well?

Blender supports custom object properties. We could use those to store various parameters (for example physics, storage or open-world related)  and have them picked up by the exporter.

You could still make a limited direct .obj to .csl translator if you like, but i personally would not consider that high priority.

Compressed binary format when/how?

Summary: It is IMHO much simpler to write ONE exporter and ONE fast parser and interpreter for a flexible file format suited to our engine capabilities than limiting ourselves to any specific generic asset format. We would need to convert to our internal format anyways unless we completely rewrite everything yet again.
Do you need any more arguments or are these enough?

Ok ok, I get it. No obj parser :D


[eslint-comments/no-use]: Allow "eslint-disable" only for selected rules (feature request)

Thx for the plugin.
Is it possible to add "allowEslintDisable" setting that will accept an array of rule names?
Motivation:
Consider "vue/no-bare-strings-in-template" rule that requires that all strings inside template are taken from language file.
Imagine that you have a static untranslated page (e.g. privacy, etc).
In this case, you want to disable "vue/no-bare-strings-in-template" rule for the entire file.
However you may not want to allow global disabling for all other rules.
In this case "allowEslintDisable" option may be helpful.
Similar settings may be added for other allowed syntaxes (e.g. eslint-disable-next-line)

Hi. I think you can allow /*eslint-disable*/ with no-use and use no-restricted-disable.
{
    "no-restricted-disable": [
        "error",
        "*",
        "!vue/no-bare-strings-in-template"
    ]
}

https://mysticatea.github.io/eslint-plugin-eslint-comments/rules/no-restricted-disable.html

Hi, thx for the hint.
First, I tried to use "no-restricted-disable" and it works for rules without slash:
"eslint-comments/no-restricted-disable": [
      "warn",
      "*",
      "!no-console"
    ],

but does not work for rules with slash (e.g. "vue/no-bare-strings-in-template")
Second, "no-restricted-disable" disallows disabling rule altogether.
What I want is to restrict which rule can be disabled for entire file, while allowing any rule to be disabled per line.

but does not work for rules with slash (e.g. "vue/no-bare-strings-in-template")

I did not know that 😅

What I want is to restrict which rule can be disabled for entire file, while allowing any rule to be disabled per line.

Does that mean that you want to set the rules that can be used with eslint-disable and the rules that can be used with eslint-disable-next-line separately? If so, that may not be possible now.

Does that mean that you want to set the rules that can be used with eslint-disable and the rules that can be used with eslint-disable-next-line separately?

Yes.
I prefer eslint-disable to be allowed only for selected rules, while eslint-disable-next-line can be allowed for all rules.
I hope this makes sence.

If so, that may not be possible now.

I see that. This is why I am suggesting new feature.

Hi @iliubinskii!
Since this repo is unmaintained, you might want to re-open this issue in the @eslint-community fork https://github.com/eslint-community/eslint-plugin-eslint-comments
For more info about why we created this organization, you can read https://eslint.org/blog/2023/03/announcing-eslint-community-org


Adding run.sh.conf for environment variables

This PR adds run.sh.conf (primarily), for the purpose of freezing the environment variables we want to be using. With this, you can simply run:
./run.sh make update_repo

To update the repo using the dev image.

Thanks @matentzn. Will OAK make any changes to run.sh.conf in the future?

run.sh.conf is not managed by ODK at all. It is just a cheap way for us to make sure that we all use the same environment variables when running, say, update_repo. It is only ever changed manually!