text:
HapticGloveModule segfaults on closure

Here the valgrind output
ergocub@ergocub-torso:~$ valgrind HapticGloveModule --GENERAL::getHumanMotionRange 0 --GENERAL::waitingDurationTime 0.0 --GENERAL::calibrationTimePeriod 0.1 --GENERAL::robotInitializationTime 1.0
==6959== Memcheck, a memory error detector
==6959== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==6959== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==6959== Command: HapticGloveModule --GENERAL::getHumanMotionRange 0 --GENERAL::waitingDurationTime 0.0 --GENERAL::calibrationTimePeriod 0.1 --GENERAL::robotInitializationTime 1.0
==6959==
[INFO] HapticGloveModule::  use the left hand:  true
[INFO] HapticGloveModule::  use the right hand:  true
[INFO] HapticGloveModule::  enable logger:  true
==6959== Invalid read of size 8
==6959==    at 0x40286A8: strncmp (strcmp.S:172)
==6959==    by 0x400668D: is_dst (dl-load.c:216)
==6959==    by 0x400810E: _dl_dst_count (dl-load.c:253)
==6959==    by 0x400810E: expand_dynamic_string_token (dl-load.c:395)
==6959==    by 0x40082B7: fillin_rpath.isra.0 (dl-load.c:483)
==6959==    by 0x4008602: decompose_rpath (dl-load.c:654)
==6959==    by 0x400ABF5: cache_rpath (dl-load.c:696)
==6959==    by 0x400ABF5: cache_rpath (dl-load.c:677)
==6959==    by 0x400ABF5: _dl_map_object (dl-load.c:2165)
==6959==    by 0x4003494: openaux (dl-deps.c:64)
==6959==    by 0x5182A97: _dl_catch_exception (dl-error-skeleton.c:208)
==6959==    by 0x4003C7B: _dl_map_object_deps (dl-deps.c:248)
==6959==    by 0x400EA0E: dl_open_worker_begin (dl-open.c:592)
==6959==    by 0x5182A97: _dl_catch_exception (dl-error-skeleton.c:208)
==6959==    by 0x400DF99: dl_open_worker (dl-open.c:782)
==6959==  Address 0xf0b7a11 is 33 bytes inside a block of size 36 alloc'd
==6959==    at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==6959==    by 0x40271DF: malloc (rtld-malloc.h:56)
==6959==    by 0x40271DF: strdup (strdup.c:42)
==6959==    by 0x4008594: decompose_rpath (dl-load.c:629)
==6959==    by 0x400ABF5: cache_rpath (dl-load.c:696)
==6959==    by 0x400ABF5: cache_rpath (dl-load.c:677)
==6959==    by 0x400ABF5: _dl_map_object (dl-load.c:2165)
==6959==    by 0x4003494: openaux (dl-deps.c:64)
==6959==    by 0x5182A97: _dl_catch_exception (dl-error-skeleton.c:208)
==6959==    by 0x4003C7B: _dl_map_object_deps (dl-deps.c:248)
==6959==    by 0x400EA0E: dl_open_worker_begin (dl-open.c:592)
==6959==    by 0x5182A97: _dl_catch_exception (dl-error-skeleton.c:208)
==6959==    by 0x400DF99: dl_open_worker (dl-open.c:782)
==6959==    by 0x5182A97: _dl_catch_exception (dl-error-skeleton.c:208)
==6959==    by 0x400E34D: _dl_open (dl-open.c:883)
==6959==
==6959== Invalid read of size 8
==6959==    at 0x40286A8: strncmp (strcmp.S:172)
==6959==    by 0x400668D: is_dst (dl-load.c:216)
==6959==    by 0x4007F79: _dl_dst_substitute (dl-load.c:295)
==6959==    by 0x40082B7: fillin_rpath.isra.0 (dl-load.c:483)
==6959==    by 0x4008602: decompose_rpath (dl-load.c:654)
==6959==    by 0x400ABF5: cache_rpath (dl-load.c:696)
==6959==    by 0x400ABF5: cache_rpath (dl-load.c:677)
==6959==    by 0x400ABF5: _dl_map_object (dl-load.c:2165)
==6959==    by 0x4003494: openaux (dl-deps.c:64)
==6959==    by 0x5182A97: _dl_catch_exception (dl-error-skeleton.c:208)
==6959==    by 0x4003C7B: _dl_map_object_deps (dl-deps.c:248)
==6959==    by 0x400EA0E: dl_open_worker_begin (dl-open.c:592)
==6959==    by 0x5182A97: _dl_catch_exception (dl-error-skeleton.c:208)
==6959==    by 0x400DF99: dl_open_worker (dl-open.c:782)
==6959==  Address 0xf0b7a11 is 33 bytes inside a block of size 36 alloc'd
==6959==    at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==6959==    by 0x40271DF: malloc (rtld-malloc.h:56)
==6959==    by 0x40271DF: strdup (strdup.c:42)
==6959==    by 0x4008594: decompose_rpath (dl-load.c:629)
==6959==    by 0x400ABF5: cache_rpath (dl-load.c:696)
==6959==    by 0x400ABF5: cache_rpath (dl-load.c:677)
==6959==    by 0x400ABF5: _dl_map_object (dl-load.c:2165)
==6959==    by 0x4003494: openaux (dl-deps.c:64)
==6959==    by 0x5182A97: _dl_catch_exception (dl-error-skeleton.c:208)
==6959==    by 0x4003C7B: _dl_map_object_deps (dl-deps.c:248)
==6959==    by 0x400EA0E: dl_open_worker_begin (dl-open.c:592)
==6959==    by 0x5182A97: _dl_catch_exception (dl-error-skeleton.c:208)
==6959==    by 0x400DF99: dl_open_worker (dl-open.c:782)
==6959==    by 0x5182A97: _dl_catch_exception (dl-error-skeleton.c:208)
==6959==    by 0x400E34D: _dl_open (dl-open.c:883)
==6959==
[INFO] |yarp.os.Port|/HapticGloveRetargeting/logger/measures:o| Port /HapticGloveRetargeting/logger/measures:o active at tcp://10.0.2.12:10195/
[INFO] |yarp.os.Port|/HapticGloveRetargeting/logger/rpc:i| Port /HapticGloveRetargeting/logger/rpc:i active at tcp://10.0.2.12:10196/
[INFO] Teleoperation::LeftHand::  calibration time period:  0.1
[INFO] Teleoperation::LeftHand::  move the robot:  true
[INFO] Teleoperation::LeftHand::  use the robot fingertip skin:  false
[DEBUG] |yarp.dev.PolyDriver|remotecontrolboardremapper| Parameters are (REMOTE_CONTROLBOARD_OPTIONS) (axesNames (l_thumb_add l_thumb_oc l_index_oc l_middle_oc l_ring_pinky_oc)) (device remotecontrolboardremapper) (localPortPrefix "/ergocub/remoteControlBoard") (remoteControlBoards ("/ergocub/left_arm"))
[DEBUG] |yarp.dev.PolyDriver|remote_controlboard| Parameters are (device remote_controlboard) (local "/ergocub/remoteControlBoard/ergocub/left_arm") (remote "/ergocub/left_arm")
[INFO] |yarp.os.Port|/ergocub/remoteControlBoard/ergocub/left_arm/rpc:o| Port /ergocub/remoteControlBoard/ergocub/left_arm/rpc:o active at tcp://10.0.2.12:10197/
[INFO] |yarp.os.Port|/ergocub/remoteControlBoard/ergocub/left_arm/command:o| Port /ergocub/remoteControlBoard/ergocub/left_arm/command:o active at tcp://10.0.2.12:10198/
[INFO] |yarp.os.Port|/ergocub/remoteControlBoard/ergocub/left_arm/stateExt:i| Port /ergocub/remoteControlBoard/ergocub/left_arm/stateExt:i active at tcp://10.0.2.12:10199/
[INFO] |yarp.os.impl.PortCoreOutputUnit|/ergocub/remoteControlBoard/ergocub/left_arm/rpc:o| Sending output from /ergocub/remoteControlBoard/ergocub/left_arm/rpc:o to /ergocub/left_arm/rpc:i using tcp
[INFO] |yarp.os.impl.PortCoreOutputUnit|/ergocub/remoteControlBoard/ergocub/left_arm/command:o| Sending output from /ergocub/remoteControlBoard/ergocub/left_arm/command:o to /ergocub/left_arm/command:i using udp
[INFO] |yarp.os.impl.PortCoreInputUnit|/ergocub/remoteControlBoard/ergocub/left_arm/stateExt:i| Receiving input from /ergocub/left_arm/stateExt:o to /ergocub/remoteControlBoard/ergocub/left_arm/stateExt:i using udp
[INFO] |yarp.dev.PolyDriver|remote_controlboard| Created device <remote_controlboard>. See C++ class RemoteControlBoard for documentation.
[INFO] |yarp.dev.PolyDriver|remotecontrolboardremapper| Created device <remotecontrolboardremapper>. See C++ class RemoteControlBoardRemapper for documentation.
[INFO] RobotInterface::LeftHand::  initialization time [sec]: 1 , steady state counter threshold [steps]: 5 , steady state threshold [rad]: 0.05
[INFO] RobotInterface::LeftHand::  the necessary time for initialization is:  1  seconds.
[WARNING] RobotInterface::LeftHand::  unable to initialize the robot axis values in  1 seconds; but continuing.
[INFO] RobotInterface::LeftHand::  actuated axis: [l_thumb_add, l_thumb_oc, l_index_oc, l_middle_oc, l_ring_pinky_oc]
[INFO] RobotInterface::LeftHand::  actuated joints: [l_thumb_add, l_thumb_oc, l_index_oc, l_middle_oc, l_ring_pinky_oc]
[INFO] RobotInterface::LeftHand::  actuated joint info l_thumb_add  ,use analog: false  ,index:  0  ,scale: 1
[INFO] RobotInterface::LeftHand::  actuated joint info l_thumb_oc  ,use analog: false  ,index:  1  ,scale: 1
[INFO] RobotInterface::LeftHand::  actuated joint info l_index_oc  ,use analog: false  ,index:  2  ,scale: 1
[INFO] RobotInterface::LeftHand::  actuated joint info l_middle_oc  ,use analog: false  ,index:  3  ,scale: 1
[INFO] RobotInterface::LeftHand::  actuated joint info l_ring_pinky_oc  ,use analog: false  ,index:  4  ,scale: 1
[INFO] RobotInterface::LeftHand::  m_noAllAxis:  6
[INFO] RobotInterface::LeftHand::  m_noAllJoints:  6
[INFO] RobotInterface::LeftHand::  m_allAxisNames:  [l_thumb_add, l_thumb_oc, l_index_add, l_index_oc, l_middle_oc, l_ring_pinky_oc]
[INFO] RobotInterface::LeftHand::  m_allJointNames:  [l_thumb_add, l_thumb_oc, l_index_add, l_index_oc, l_middle_oc, l_ring_pinky_oc]
[INFO] RobotController::LeftHand::  number of all axis 6
[INFO] RobotController::LeftHand::  number of actuated axis 5
[INFO] RobotController::LeftHand::  number of all joints:  6
[INFO] RobotController::LeftHand::  number of actuated joints:  5
[INFO] RobotController::LeftHand::  axes and joints of the robot are coupled:  false
[INFO] RobotController::LeftHand::  the coupling model between the robot axes and joints should be found:  false
[INFO] RobotController::LeftHand::  robot controller exponential filter gain:  0.9
[INFO] RobotController::LeftHand::  configuration is done.
[DEBUG] |yarp.dev.PolyDriver|iwear_remapper| Parameters are (carrier fast_tcp) (device iwear_remapper) (wearableDataPorts ("/WearableData/HapticGlove/LeftHand/data:o"))
[INFO] IWearRemapper : Cannot find a suitable allowDynamicData parameter, using default value.
[INFO] IWearRemapper : Using allowDynamicData parameter: true
[INFO] IWearRemapper : *** ========================
[INFO] IWearRemapper : *** Wearable Data Port 1   : /WearableData/HapticGlove/LeftHand/data:o
[INFO] IWearRemapper : *** ========================
[DEBUG] IWearRemapper : Configuring input data ports
[INFO] |yarp.os.Port|/tmp/port/7| Port /tmp/port/7 active at tcp://10.0.2.12:10208/
[DEBUG] IWearRemapper : Opening input ports
[INFO] |yarp.os.impl.PortCoreInputUnit|/tmp/port/7| Receiving input from /WearableData/HapticGlove/LeftHand/data:o to /tmp/port/7 using fast_tcp
[DEBUG] IWearRemapper : Opened correctly
[INFO] |yarp.dev.PolyDriver|iwear_remapper| Created device <iwear_remapper>. See C++ class wearable::devices::IWearRemapper for documentation.
[INFO] GloveWearableImpl::LeftHand::  IWear interface waiting for first data. Waiting...
[INFO] GloveWearableImpl::LeftHand::  IWear interface waiting for first data. Waiting...
[INFO] Attached wearable device name :  IWearRemapper::
[INFO] |yarp.os.Port|/WearableData/HapticGlove/LeftHand/Actuators/input:o| Port /WearableData/HapticGlove/LeftHand/Actuators/input:o active at tcp://10.0.2.12:10200/
[INFO] |yarp.os.impl.PortCoreOutputUnit|/WearableData/HapticGlove/LeftHand/Actuators/input:o| Sending output from /WearableData/HapticGlove/LeftHand/Actuators/input:o to /WearableData/HapticGlove/LeftHand/Actuators/input:i using fast_tcp
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vLink::l_hand
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vLink::l_thumb_finger::fingertip
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vLink::l_index_finger::fingertip
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vLink::l_middle_finger::fingertip
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vLink::l_ring_finger::fingertip
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vLink::l_little_finger::fingertip
[INFO] GloveWearableImpl::LeftHand::  size of the fingertip link sensors:  5
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_thumb_oppose
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_thumb_proximal
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_thumb_middle
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_thumb_distal
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_index_abduction
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_index_proximal
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_index_middle
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_index_distal
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_middle_abduction
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_middle_proximal
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_middle_middle
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_middle_distal
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_ring_abduction
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_ring_proximal
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_ring_middle
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_ring_distal
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_pinky_abduction
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_pinky_proximal
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_pinky_middle
[INFO] GloveWearableImpl::LeftHand::  initialize the following sensor:  HapticGlove::vJoint::l_pinky_distal
[INFO] GloveWearableImpl::LeftHand::  size of the joint sensors:  20
[INFO] GloveWearableImpl::LeftHand::  initialization of the wearable sensors is done.
[INFO] GloveWearableImpl::LeftHand::  configuration is done.
[INFO] GloveControlHelper::LeftHand::  configuration is done.
[WARNING] Retargeting::LeftHand::  in robot_to_human_map found non-exising robot joint  l_index_add
[INFO] Retargeting::LeftHand::  m_gainValueError:  [0, 15, 15, 15, 15]
[INFO] Retargeting::LeftHand::  m_gainVelocityError:  [0, 0.1, 0.1, 0.1, 0.1]
[INFO] Retargeting::LeftHand::  m_gainVibrotactile:  [0.8, 0.8, 0.8, 0.8, 0.8]
[INFO] Retargeting::LeftHand::  m_retargetingScaling:  [-1, 1, 1, 1, 1]
[INFO] Retargeting::LeftHand::  m_retargetingBias:  [0, 0, 0, 0, 0]
[INFO] Retargeting::LeftHand::  m_fingerAxesMap:  0  ::  [0, 1]
[INFO] Retargeting::LeftHand::  m_fingerAxesMap:  1  ::  [2]
[INFO] Retargeting::LeftHand::  m_fingerAxesMap:  2  ::  [3]
[INFO] Retargeting::LeftHand::  m_fingerAxesMap:  3  ::  [4]
[INFO] Retargeting::LeftHand::  m_fingerAxesMap:  4  ::  [4]
[INFO] Retargeting::LeftHand::  m_robotToHumanJointIndicesMap:  l_thumb_add 0 :: 0
[INFO] Retargeting::LeftHand::  m_robotToHumanJointIndicesMap:  l_thumb_oc 1 :: 3
[INFO] Retargeting::LeftHand::  m_robotToHumanJointIndicesMap:  l_index_oc 2 :: 7
[INFO] Retargeting::LeftHand::  m_robotToHumanJointIndicesMap:  l_middle_oc 3 :: 11
[INFO] Retargeting::LeftHand::  m_robotToHumanJointIndicesMap:  l_ring_pinky_oc 4 :: 15
[INFO] Retargeting::LeftHand::  configuration is done.
[INFO] Retargeting::LeftHand::  m_robotAxesRangeMin [rad]:  [0.000191748, 0.000191748, 0.000191748, 0.000191748, 0.000191748]
[INFO] Retargeting::LeftHand::  m_robotAxesRangeMax [rad]:  [1.57061, 1.57061, 1.57061, 1.57061, 1.57061]
[INFO] Retargeting::LeftHand::  m_robotJointsRangeMin [rad]:  [0.000191748, 0.000191748, 0.000191748, 0.000191748, 0.000191748]
[INFO] Retargeting::LeftHand::  m_robotJointsRangeMax [rad]:  [1.57061, 1.57061, 1.57061, 1.57061, 1.57061]
[INFO] |yarp.os.Port|/LeftHand/hapticGloveTeleoperation/rpc| Port /LeftHand/hapticGloveTeleoperation/rpc active at tcp://10.0.2.12:10201/
[INFO] Teleoperation::LeftHand::  enable the logger:  true
[INFO] Teleoperation::LeftHand::  configuration is done.
[INFO] Teleoperation::RightHand::  calibration time period:  0.1
[INFO] Teleoperation::RightHand::  move the robot:  true
[INFO] Teleoperation::RightHand::  use the robot fingertip skin:  false
[DEBUG] |yarp.dev.PolyDriver|remotecontrolboardremapper| Parameters are (REMOTE_CONTROLBOARD_OPTIONS) (axesNames (r_thumb_add r_thumb_oc r_index_oc r_middle_oc r_ring_pinky_oc)) (device remotecontrolboardremapper) (localPortPrefix "/ergocub/remoteControlBoard") (remoteControlBoards ("/ergocub/right_arm"))
[DEBUG] |yarp.dev.PolyDriver|remote_controlboard| Parameters are (device remote_controlboard) (local "/ergocub/remoteControlBoard/ergocub/right_arm") (remote "/ergocub/right_arm")
[INFO] |yarp.os.Port|/ergocub/remoteControlBoard/ergocub/right_arm/rpc:o| Port /ergocub/remoteControlBoard/ergocub/right_arm/rpc:o active at tcp://10.0.2.12:10202/
[INFO] |yarp.os.Port|/ergocub/remoteControlBoard/ergocub/right_arm/command:o| Port /ergocub/remoteControlBoard/ergocub/right_arm/command:o active at tcp://10.0.2.12:10203/
[INFO] |yarp.os.Port|/ergocub/remoteControlBoard/ergocub/right_arm/stateExt:i| Port /ergocub/remoteControlBoard/ergocub/right_arm/stateExt:i active at tcp://10.0.2.12:10204/
[INFO] |yarp.os.impl.PortCoreOutputUnit|/ergocub/remoteControlBoard/ergocub/right_arm/rpc:o| Sending output from /ergocub/remoteControlBoard/ergocub/right_arm/rpc:o to /ergocub/right_arm/rpc:i using tcp
[INFO] |yarp.os.impl.PortCoreOutputUnit|/ergocub/remoteControlBoard/ergocub/right_arm/command:o| Sending output from /ergocub/remoteControlBoard/ergocub/right_arm/command:o to /ergocub/right_arm/command:i using udp
[INFO] |yarp.os.impl.PortCoreInputUnit|/ergocub/remoteControlBoard/ergocub/right_arm/stateExt:i| Receiving input from /ergocub/right_arm/stateExt:o to /ergocub/remoteControlBoard/ergocub/right_arm/stateExt:i using udp
[INFO] |yarp.dev.PolyDriver|remote_controlboard| Created device <remote_controlboard>. See C++ class RemoteControlBoard for documentation.
[INFO] |yarp.dev.PolyDriver|remotecontrolboardremapper| Created device <remotecontrolboardremapper>. See C++ class RemoteControlBoardRemapper for documentation.
[INFO] RobotInterface::RightHand::  initialization time [sec]: 1 , steady state counter threshold [steps]: 5 , steady state threshold [rad]: 0.05
[INFO] RobotInterface::RightHand::  the necessary time for initialization is:  1  seconds.
[WARNING] RobotInterface::RightHand::  unable to initialize the robot axis values in  1 seconds; but continuing.
[INFO] RobotInterface::RightHand::  actuated axis: [r_thumb_add, r_thumb_oc, r_index_oc, r_middle_oc, r_ring_pinky_oc]
[INFO] RobotInterface::RightHand::  actuated joints: [r_thumb_add, r_thumb_oc, r_index_oc, r_middle_oc, r_ring_pinky_oc]
[INFO] RobotInterface::RightHand::  actuated joint info r_thumb_add  ,use analog: false  ,index:  0  ,scale: 1
[INFO] RobotInterface::RightHand::  actuated joint info r_thumb_oc  ,use analog: false  ,index:  1  ,scale: 1
[INFO] RobotInterface::RightHand::  actuated joint info r_index_oc  ,use analog: false  ,index:  2  ,scale: 1
[INFO] RobotInterface::RightHand::  actuated joint info r_middle_oc  ,use analog: false  ,index:  3  ,scale: 1
[INFO] RobotInterface::RightHand::  actuated joint info r_ring_pinky_oc  ,use analog: false  ,index:  4  ,scale: 1
[INFO] RobotInterface::RightHand::  m_noAllAxis:  6
[INFO] RobotInterface::RightHand::  m_noAllJoints:  6
[INFO] RobotInterface::RightHand::  m_allAxisNames:  [r_thumb_add, r_thumb_oc, r_index_add, r_index_oc, r_middle_oc, r_ring_pinky_oc]
[INFO] RobotInterface::RightHand::  m_allJointNames:  [r_thumb_add, r_thumb_oc, r_index_add, r_index_oc, r_middle_oc, r_ring_pinky_oc]
[INFO] RobotController::RightHand::  number of all axis 6
[INFO] RobotController::RightHand::  number of actuated axis 5
[INFO] RobotController::RightHand::  number of all joints:  6
[INFO] RobotController::RightHand::  number of actuated joints:  5
[INFO] RobotController::RightHand::  axes and joints of the robot are coupled:  false
[INFO] RobotController::RightHand::  the coupling model between the robot axes and joints should be found:  false
[INFO] RobotController::RightHand::  robot controller exponential filter gain:  0.9
[INFO] RobotController::RightHand::  configuration is done.
[DEBUG] |yarp.dev.PolyDriver|iwear_remapper| Parameters are (carrier fast_tcp) (device iwear_remapper) (wearableDataPorts ("/WearableData/HapticGlove/RightHand/data:o"))
[INFO] IWearRemapper : Cannot find a suitable allowDynamicData parameter, using default value.
[INFO] IWearRemapper : Using allowDynamicData parameter: true
[INFO] IWearRemapper : *** ========================
[INFO] IWearRemapper : *** Wearable Data Port 1   : /WearableData/HapticGlove/RightHand/data:o
[INFO] IWearRemapper : *** ========================
[DEBUG] IWearRemapper : Configuring input data ports
[INFO] |yarp.os.Port|/tmp/port/8| Port /tmp/port/8 active at tcp://10.0.2.12:10296/
[DEBUG] IWearRemapper : Opening input ports
[INFO] |yarp.os.impl.PortCoreInputUnit|/tmp/port/8| Receiving input from /WearableData/HapticGlove/RightHand/data:o to /tmp/port/8 using fast_tcp
[DEBUG] IWearRemapper : Opened correctly
[INFO] |yarp.dev.PolyDriver|iwear_remapper| Created device <iwear_remapper>. See C++ class wearable::devices::IWearRemapper for documentation.
[INFO] GloveWearableImpl::RightHand::  IWear interface waiting for first data. Waiting...
[INFO] Attached wearable device name :  IWearRemapper::
[INFO] |yarp.os.Port|/WearableData/HapticGlove/RightHand/Actuators/input:o| Port /WearableData/HapticGlove/RightHand/Actuators/input:o active at tcp://10.0.2.12:10206/
[INFO] |yarp.os.impl.PortCoreOutputUnit|/WearableData/HapticGlove/RightHand/Actuators/input:o| Sending output from /WearableData/HapticGlove/RightHand/Actuators/input:o to /WearableData/HapticGlove/RightHand/Actuators/input:i using fast_tcp
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vLink::r_hand
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vLink::r_thumb_finger::fingertip
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vLink::r_index_finger::fingertip
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vLink::r_middle_finger::fingertip
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vLink::r_ring_finger::fingertip
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vLink::r_little_finger::fingertip
[INFO] GloveWearableImpl::RightHand::  size of the fingertip link sensors:  5
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_thumb_oppose
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_thumb_proximal
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_thumb_middle
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_thumb_distal
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_index_abduction
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_index_proximal
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_index_middle
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_index_distal
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_middle_abduction
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_middle_proximal
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_middle_middle
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_middle_distal
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_ring_abduction
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_ring_proximal
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_ring_middle
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_ring_distal
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_pinky_abduction
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_pinky_proximal
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_pinky_middle
[INFO] GloveWearableImpl::RightHand::  initialize the following sensor:  HapticGlove::vJoint::r_pinky_distal
[INFO] GloveWearableImpl::RightHand::  size of the joint sensors:  20
[INFO] GloveWearableImpl::RightHand::  initialization of the wearable sensors is done.
[INFO] GloveWearableImpl::RightHand::  configuration is done.
[INFO] GloveControlHelper::RightHand::  configuration is done.
[WARNING] Retargeting::RightHand::  in robot_to_human_map found non-exising robot joint  r_index_add
[INFO] Retargeting::RightHand::  m_gainValueError:  [0, 15, 15, 15, 15]
[INFO] Retargeting::RightHand::  m_gainVelocityError:  [0, 0.1, 0.1, 0.1, 0.1]
[INFO] Retargeting::RightHand::  m_gainVibrotactile:  [0.8, 0.8, 0.8, 0.8, 0.8]
[INFO] Retargeting::RightHand::  m_retargetingScaling:  [1, 1, 1, 1, 1]
[INFO] Retargeting::RightHand::  m_retargetingBias:  [0, 0, 0, 0, 0]
[INFO] Retargeting::RightHand::  m_fingerAxesMap:  0  ::  [0, 1]
[INFO] Retargeting::RightHand::  m_fingerAxesMap:  1  ::  [2]
[INFO] Retargeting::RightHand::  m_fingerAxesMap:  2  ::  [3]
[INFO] Retargeting::RightHand::  m_fingerAxesMap:  3  ::  [4]
[INFO] Retargeting::RightHand::  m_fingerAxesMap:  4  ::  [4]
[INFO] Retargeting::RightHand::  m_robotToHumanJointIndicesMap:  r_thumb_add 0 :: 0
[INFO] Retargeting::RightHand::  m_robotToHumanJointIndicesMap:  r_thumb_oc 1 :: 3
[INFO] Retargeting::RightHand::  m_robotToHumanJointIndicesMap:  r_index_oc 2 :: 7
[INFO] Retargeting::RightHand::  m_robotToHumanJointIndicesMap:  r_middle_oc 3 :: 11
[INFO] Retargeting::RightHand::  m_robotToHumanJointIndicesMap:  r_ring_pinky_oc 4 :: 15
[INFO] Retargeting::RightHand::  configuration is done.
[INFO] Retargeting::RightHand::  m_robotAxesRangeMin [rad]:  [0.000191748, 0.000191748, 0.000191748, 0.000191748, 0.000191748]
[INFO] Retargeting::RightHand::  m_robotAxesRangeMax [rad]:  [1.57061, 1.57061, 1.57061, 1.57061, 1.57061]
[INFO] Retargeting::RightHand::  m_robotJointsRangeMin [rad]:  [0.000191748, 0.000191748, 0.000191748, 0.000191748, 0.000191748]
[INFO] Retargeting::RightHand::  m_robotJointsRangeMax [rad]:  [1.57061, 1.57061, 1.57061, 1.57061, 1.57061]
[INFO] |yarp.os.Port|/RightHand/hapticGloveTeleoperation/rpc| Port /RightHand/hapticGloveTeleoperation/rpc active at tcp://10.0.2.12:10207/
[INFO] Teleoperation::RightHand::  enable the logger:  true
[INFO] Teleoperation::RightHand::  configuration is done.
[INFO] HapticGloveModule::  configuration is done.
[INFO] RobotController::LeftHand::  axes and joints are not coupled, so returning.
[INFO] Teleoperation::RightHand::  data collected to learn robot model.
[INFO] Teleoperation::LeftHand::  data collected to learn robot model.
[INFO] Teleoperation::RightHand::  data collected to learn robot model.
[WARNING] Teleoperation::RightHand::  at this point estimators are not supposed to be initialized.
[WARNING] HapticGloveModule::  unable to prepare the right hand.
^C[INFO] |yarp.os.RFModule| [try 1 of 3] Trying to shut down.
[INFO] |yarp.os.RFModule| RFModule closing.
[INFO] HapticGloveModule::  trying to close.
[INFO] Teleoperation::LeftHand::  trying to close.
[INFO] RobotInterface::LeftHand::  closing.
[INFO] RobotInterface::LeftHand::  the necessary time for initialization is:  3  seconds.
[WARNING] RobotInterface::LeftHand::  unable to initialize the robot axis values in  3 seconds; but continuing.
[INFO] |yarp.os.impl.PortCoreOutputUnit|/ergocub/remoteControlBoard/ergocub/left_arm/rpc:o| Removing output from /ergocub/remoteControlBoard/ergocub/left_arm/rpc:o to /ergocub/left_arm/rpc:i
[INFO] |yarp.os.impl.PortCoreOutputUnit|/ergocub/remoteControlBoard/ergocub/left_arm/command:o| output for route /ergocub/remoteControlBoard/ergocub/left_arm/command:o->udp->/ergocub/left_arm/command:i asking other side to close by out-of-band means
[INFO] |yarp.os.impl.PortCoreOutputUnit|/ergocub/remoteControlBoard/ergocub/left_arm/command:o| Removing output from /ergocub/remoteControlBoard/ergocub/left_arm/command:o to /ergocub/left_arm/command:i
[INFO] |yarp.os.impl.PortCoreInputUnit|/ergocub/remoteControlBoard/ergocub/left_arm/stateExt:i| Removing input from /ergocub/left_arm/stateExt:o to /ergocub/remoteControlBoard/ergocub/left_arm/stateExt:i
[WARNING] RobotInterface::LeftHand::  Unable to close the analogsensorclient device.
[INFO] RobotInterface::LeftHand::  closed badly .
[WARNING] Teleoperation::LeftHand::  unable to close the robot controller.
[INFO] GloveControlHelper::LeftHand::  trying to close
[INFO] GloveWearableImpl::LeftHand::  closing the glove wearable implementation.
==6959== Thread 11:
==6959== Invalid read of size 1
==6959==    at 0x4B61EBE: yarp::os::idl::WireReader::~WireReader() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x14EDFE36: wearable::msg::WearableData::read(yarp::os::ConnectionReader&) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libWearableData.so)
==6959==    by 0x4B0D390: yarp::os::PortReaderBufferBase::read(yarp::os::ConnectionReader&) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BBA240: yarp::os::impl::PortCore::readBlock(yarp::os::ConnectionReader&, void*, yarp::os::OutputStream*) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BC4A2E: yarp::os::impl::PortCoreInputUnit::run() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BDD9FC: theExecutiveBranch(void*) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4DB5252: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30)
==6959==    by 0x50A2AC2: start_thread (pthread_create.c:442)
==6959==    by 0x5133A03: clone (clone.S:100)
==6959==  Address 0x16712118 is on thread 11's stack
==6959==  136 bytes below stack pointer
==6959==
[INFO] |yarp.os.impl.PortCoreInputUnit|/tmp/port/7| Removing input from /WearableData/HapticGlove/LeftHand/data:o to /tmp/port/7
[INFO] |yarp.os.impl.PortCoreOutputUnit|/WearableData/HapticGlove/LeftHand/Actuators/input:o| Removing output from /WearableData/HapticGlove/LeftHand/Actuators/input:o to /WearableData/HapticGlove/LeftHand/Actuators/input:i
[INFO] GloveControlHelper::LeftHand::  closed Successfully .
[INFO] Retargeting::LeftHand::  closing.
[INFO] Teleoperation::LeftHand::  closed badly .
[WARNING] HapticGloveModule::  unable to close left hand teleoperation.
[INFO] Teleoperation::RightHand::  trying to close.
[INFO] RobotInterface::RightHand::  closing.
[INFO] RobotInterface::RightHand::  the necessary time for initialization is:  3  seconds.
[WARNING] RobotInterface::RightHand::  unable to initialize the robot axis values in  3 seconds; but continuing.
[INFO] |yarp.os.impl.PortCoreOutputUnit|/ergocub/remoteControlBoard/ergocub/right_arm/rpc:o| Removing output from /ergocub/remoteControlBoard/ergocub/right_arm/rpc:o to /ergocub/right_arm/rpc:i
[INFO] |yarp.os.impl.PortCoreOutputUnit|/ergocub/remoteControlBoard/ergocub/right_arm/command:o| output for route /ergocub/remoteControlBoard/ergocub/right_arm/command:o->udp->/ergocub/right_arm/command:i asking other side to close by out-of-band means
[INFO] |yarp.os.impl.PortCoreOutputUnit|/ergocub/remoteControlBoard/ergocub/right_arm/command:o| Removing output from /ergocub/remoteControlBoard/ergocub/right_arm/command:o to /ergocub/right_arm/command:i
[INFO] |yarp.os.impl.PortCoreInputUnit|/ergocub/remoteControlBoard/ergocub/right_arm/stateExt:i| Removing input from /ergocub/right_arm/stateExt:o to /ergocub/remoteControlBoard/ergocub/right_arm/stateExt:i
[WARNING] RobotInterface::RightHand::  Unable to close the analogsensorclient device.
[INFO] RobotInterface::RightHand::  closed badly .
[WARNING] Teleoperation::RightHand::  unable to close the robot controller.
[INFO] GloveControlHelper::RightHand::  trying to close
[INFO] GloveWearableImpl::RightHand::  closing the glove wearable implementation.
[INFO] |yarp.os.impl.PortCoreInputUnit|/tmp/port/8| Removing input from /WearableData/HapticGlove/RightHand/data:o to /tmp/port/8
[INFO] |yarp.os.impl.PortCoreOutputUnit|/WearableData/HapticGlove/RightHand/Actuators/input:o| Removing output from /WearableData/HapticGlove/RightHand/Actuators/input:o to /WearableData/HapticGlove/RightHand/Actuators/input:i
[INFO] GloveControlHelper::RightHand::  closed Successfully .
[INFO] Retargeting::RightHand::  closing.
[INFO] Teleoperation::RightHand::  closed badly .
[WARNING] HapticGloveModule::  unable to close right hand teleoperation.
[INFO] |yarp.os.RFModule| RFModule finished.
==6959== Thread 1:
==6959== Invalid read of size 8
==6959==    at 0x4B658A8: yarp::os::impl::BottleImpl::clear() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B658FA: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B6594C: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4ACCC28: yarp::os::Bottle::~Bottle() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BD8B6E: yarp::os::impl::StoreList::~StoreList() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B658AD: yarp::os::impl::BottleImpl::clear() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B658FA: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B6594C: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4ACCC28: yarp::os::Bottle::~Bottle() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B11889: std::_Rb_tree<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem>, std::_Select1st<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> > >::_M_erase(std::_Rb_tree_node<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >*) [clone .isra.0] (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B1184F: std::_Rb_tree<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem>, std::_Select1st<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> > >::_M_erase(std::_Rb_tree_node<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >*) [clone .isra.0] (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B1184F: std::_Rb_tree<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem>, std::_Select1st<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> > >::_M_erase(std::_Rb_tree_node<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >*) [clone .isra.0] (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==  Address 0xdaea6e0 is 0 bytes after a block of size 80 free'd
==6959==    at 0x484BB6F: operator delete(void*, unsigned long) (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==6959==    by 0x4B658AD: yarp::os::impl::BottleImpl::clear() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B658FA: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B6594C: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4ACCC28: yarp::os::Bottle::~Bottle() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BD8B6E: yarp::os::impl::StoreList::~StoreList() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B658AD: yarp::os::impl::BottleImpl::clear() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B658FA: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B6594C: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4ACCC28: yarp::os::Bottle::~Bottle() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BBA1DB: yarp::os::impl::PortCore::readBlock(yarp::os::ConnectionReader&, void*, yarp::os::OutputStream*) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BC4A2E: yarp::os::impl::PortCoreInputUnit::run() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==  Block was alloc'd at
==6959==    at 0x4849013: operator new(unsigned long) (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==6959==    by 0x4BD1D75: yarp::os::impl::Storable::createByCode(int) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B67CAE: yarp::os::impl::BottleImpl::fromBytes(yarp::os::ConnectionReader&) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B682B6: yarp::os::impl::BottleImpl::read(yarp::os::ConnectionReader&) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BD6280: yarp::os::impl::StoreList::readRaw(yarp::os::ConnectionReader&) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B67CCF: yarp::os::impl::BottleImpl::fromBytes(yarp::os::ConnectionReader&) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B682B6: yarp::os::impl::BottleImpl::read(yarp::os::ConnectionReader&) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BBA1D0: yarp::os::impl::PortCore::readBlock(yarp::os::ConnectionReader&, void*, yarp::os::OutputStream*) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BC4A2E: yarp::os::impl::PortCoreInputUnit::run() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BDD9FC: theExecutiveBranch(void*) (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4DB5252: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30)
==6959==    by 0x50A2AC2: start_thread (pthread_create.c:442)
==6959==
==6959== Invalid read of size 8
==6959==    at 0x4B658AB: yarp::os::impl::BottleImpl::clear() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B658FA: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B6594C: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4ACCC28: yarp::os::Bottle::~Bottle() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BD8B6E: yarp::os::impl::StoreList::~StoreList() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B658AD: yarp::os::impl::BottleImpl::clear() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B658FA: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B6594C: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4ACCC28: yarp::os::Bottle::~Bottle() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B11889: std::_Rb_tree<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem>, std::_Select1st<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> > >::_M_erase(std::_Rb_tree_node<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >*) [clone .isra.0] (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B1184F: std::_Rb_tree<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem>, std::_Select1st<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> > >::_M_erase(std::_Rb_tree_node<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >*) [clone .isra.0] (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B1184F: std::_Rb_tree<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem>, std::_Select1st<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> > >::_M_erase(std::_Rb_tree_node<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >*) [clone .isra.0] (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==  Address 0x203932343137353b is not stack'd, malloc'd or (recently) free'd
==6959==
==6959==
==6959== Process terminating with default action of signal 11 (SIGSEGV)
==6959==  General Protection Fault
==6959==    at 0x4B658AB: yarp::os::impl::BottleImpl::clear() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B658FA: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B6594C: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4ACCC28: yarp::os::Bottle::~Bottle() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4BD8B6E: yarp::os::impl::StoreList::~StoreList() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B658AD: yarp::os::impl::BottleImpl::clear() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B658FA: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B6594C: yarp::os::impl::BottleImpl::~BottleImpl() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4ACCC28: yarp::os::Bottle::~Bottle() (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B11889: std::_Rb_tree<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem>, std::_Select1st<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> > >::_M_erase(std::_Rb_tree_node<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >*) [clone .isra.0] (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B1184F: std::_Rb_tree<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem>, std::_Select1st<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> > >::_M_erase(std::_Rb_tree_node<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >*) [clone .isra.0] (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==    by 0x4B1184F: std::_Rb_tree<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem>, std::_Select1st<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> > >::_M_erase(std::_Rb_tree_node<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, PropertyItem> >*) [clone .isra.0] (in /usr/local/src/robot/robotology-superbuild/build/install/lib/libYARP_os.so.3.9.0)
==6959==
==6959== HEAP SUMMARY:
==6959==     in use at exit: 325,478 bytes in 1,639 blocks
==6959==   total heap usage: 2,047,455 allocs, 2,045,816 frees, 159,773,512 bytes allocated
==6959==
==6959== LEAK SUMMARY:
==6959==    definitely lost: 0 bytes in 0 blocks
==6959==    indirectly lost: 0 bytes in 0 blocks
==6959==      possibly lost: 6,464 bytes in 6 blocks
==6959==    still reachable: 316,998 bytes in 1,612 blocks
==6959==                       of which reachable via heuristic:
==6959==                         multipleinheritance: 3,312 bytes in 23 blocks
==6959==         suppressed: 0 bytes in 0 blocks
==6959== Rerun with --leak-check=full to see details of leaked memory
==6959==
==6959== For lists of detected and suppressed errors, rerun with: -s
==6959== ERROR SUMMARY: 6 errors from 5 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)

These messages seem fishy
[INFO] RobotInterface::RightHand::  closing.
[INFO] RobotInterface::RightHand::  the necessary time for initialization is:  3  seconds.

Maybe this is the time used to go back to the initial position, but I would need to check.
Also these messages are interesting
[WARNING] RobotInterface::RightHand::  Unable to close the analogsensorclient device.
[INFO] RobotInterface::RightHand::  closed badly .
[WARNING] Teleoperation::RightHand::  unable to close the robot controller.
[INFO] GloveControlHelper::RightHand::  trying to close

It seems some components are not closing gracefully.

The segmentation fault seems to occur within yarp, inside the destructor of a Bottle.

repo: robotology/walking-teleoperation


text:
refactor: separate state from control_crypto

this simplifies some pattern matches, and makes the code slightly clearer

CI error is unrelated.

source: gharchive/pull-request

authors: hannesm reynir

repo: robur-coop/miragevpn

license_type: permissive

license_source: github-api


text:
perform roc nightly installation through curl

This prevents a scary warning for MacOS users and allows us to detect CPU features and download the fastest compatible binary based on that.

Duplicate of https://github.com/roc-lang/roc/issues/3272

source: gharchive/issue

repo: roc-lang/roc


text:
Avoid alloca in libpsl and tests

alloca() needs special treatment for Windows and possibly other systems. The implementation also is compiler-specific. alloca() in general is considered "dangerous" (similar to variable-length arrays (VLAs)).
This PR drops the usage of alloca() for the aforementioned reasons.

Rebased in order to refresh CI checks, everything looks good.

authors: eli-schwartz rockdaboot

repo: rockdaboot/libpsl

license: mit

license_source: bigquery


text:
Logging: CLI -> File?

I might be alone on this one but, I think it would be great to have the CLI verbatim in the log files. It helps explain what stage Rocketeer is on (not stage like prod but part of the deploy process) and massively helps when debugging (so far).
Maybe there's a way to do this already? I'm going to look if this doesn't get attention in a day or so. Not hugely important for now :)

You should have logs of each deploy in .rocketeer/logs (or storage/logs in Laravel), is that not working properly?

Sorry this took so long to get. I wanted to set up a fresh environment and grab some fresh logs for this.
From a four-server deploy:
Saved logs to /Users/shonm/Sites/Com/deploy/.rocketeer/logs/local-full-dev-20150120_10:25:41.log
Saved logs to /Users/shonm/Sites/Com/deploy/.rocketeer/logs/local-full-dev-20150120_10:27:50.log
Saved logs to /Users/shonm/Sites/Com/deploy/.rocketeer/logs/local-full-dev-20150120_10:30:12.log
Saved logs to /Users/shonm/Sites/Com/deploy/.rocketeer/logs/local-full-dev-20150120_10:32:15.log

With this log config:
return sprintf('%s-%s-%s.log', $connections->getConnection(), $connections->getStage(), date('Ymd_H:i:s'));

Here's the log content of all four: https://gist.github.com/ShonM/8404826be33fe44c982d. What strikes me is that there's a distinct lack of connection information here. In the CLI not only do I get that, but I get to see the terminal prompt as well which reads the user, hostname, and some other information that would be quite handy to have all in just one log.
The way I thought this was supposed to work was essentially the CLI-shown output going straight into a file sans color. Is that not it?

I actually never noticed that but you're right, the output is gathered from the command, logged as is, and then passed to the Connection instance which is what adds the connection handle. Will change that

Should have more informations on develop now

What about lines like these? http://cl.ly/image/2e381X1N2s1I
The logs do indeed look much better. Thank you, that helps tons :)

authors: Anahkiasen ShonM

repo: rocketeers/rocketeer


text:
Eluktronics  Max 17

This worked great on the Evoo LP6/Eluktronics Mech 17.3
But the newer thinner chassis called the Max 17 has a different  keyboard it's actually  a much better keyboard  aside from the lights not working with your control  center. They use the same control center in Windows and are manufactured  by the same company  so maybe a driver update to the file would fix the issue.

Hi, would you mind posting the output of sudo hwinfo --usb | grep -A 3 8291 please?

I don't have that one any more I sold it and went with the Mech G3 /
Slimbook Titan. Sorry about that.
Respectfully
Kyle Norris
520-442-7091
@.***
https://www.linkedin.com/in/kyle-norris-254b932b
On Thu, Mar 3, 2022, 2:41 PM Astiak @.***> wrote:

Hi, would you mind posting the output of sudo hwinfo --usb | grep -A 3
8291 please?
—
Reply to this email directly, view it on GitHub
https://github.com/rodgomesc/avell-unofficial-control-center/issues/64#issuecomment-1058520477,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOED66UGUVCQP63CSNANL4TU6EWXDANCNFSM5JPAIY4Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***
com>

No worries, thank you for responding.

license: MIT


text:
이메일 전송 기능이 정상 작동하지 않음

으윽.. 에러가 나는데 수정이 필요하다.
사실 작업은 이미 하고있었는데 기록차 남겨둠.

이메일 피쳐는 https://github.com/roeniss/dhlottery-api/issues/12 를 염두에 둔 기능인데 해당 PR 이 클로즈되어서 이 제보도 무의미해졌다고 판단하여 클로즈

repo: roeniss/dhlottery-api


text:
Recognise async lock errors

Hi @rogierschouten! Thanks for keeping to work on this library, really appreciate :pray:
Correct me if I'm wrong, currently the only way to distinguish between async-lock errors and any error that's thrown by the wrapped async function is by using the error message:
function someAsyncFn() {}

lock.acquire(key, someAsyncFn, opts)
    .catch(function(err) {
        const isAsyncLockTimeoutError = err instanceof Error && err.message.includes('async-lock timed out')
	if (isAsyncLockTimeoutError) {
            // handle async-lock timeout error
        }
    });

IMHO it would be great if async-lock could deal with its own error classes to model anything can go wrong on the library side.
class AsyncLockError extends Error {
    constructor(message) {
        super(message);
    }
}

class AsyncLockTimeoutError extends AsyncLockError {
    constructor(queueKey) {
        super(`Async lock timeout out in queue ${async-lock timed out in queue}`);
        this.name = 'AsyncLockTimeoutError';
    }
}

This mean on the user-land side it would be much cleaner handling any async-lock error:
function someAsyncFn() {}

lock.acquire(key, someAsyncFn, opts)
    // Handle different kind of async-lock errors
    .catch(function(err) {
        if (err instanceof AsyncLockTimeoutError) {
            // do something...
        }
        if (err instanceof AsyncLockMaxOccTimeError) {
            // do something...
        }
    });

function someAsyncFn() {}

lock.acquire(key, someAsyncFn, opts)
    // Catch any kind of async-lock errors
    .catch(function(err) {
        if (err instanceof AsyncLockError) {
            // async-lock error
        } else {
            // Any error thrown by `someAsyncFn`
        }
    });

What do you think about that? I can find some time to work on this if it can help.

Would be great, I'll merge a PR.  Sorry for late reply, this year's been rough

authors: nebarf rogierschouten

repo: rogierschouten/async-lock


text:
The visualization results after training have not changed

Hello，the parameters obtained by training the new code esd_diffuser.py. Why are the images generated by using generate_images.py the same as the results of SDv1-4? The prompt I used during training was 'van Gogh', and the prompt during generation was vangogh_prompts.csv

aah we did not update the generate.py file. Good catch!
For now - please look at the inference.ipynb to see how to generate with the current code version

Thank you, I found that if I use the model parameters saved with the new version of the code directly, if I use generate_images.py line 66 unet.load_state_dict(torch.load(model_path)), it is unable to update the parameters after fine-tuning. However, this error does not affect the operation of the code. I wrote a new py file with reference to generate_images.py and inference.ipynb.I share this here hoping it will inspire others.
from diffusers import AutoencoderKL, UNet2DConditionModel, PNDMScheduler
from diffusers import LMSDiscreteScheduler
import torch
from PIL import Image
import pandas as pd
import argparse
import os
from utils.utils import *
import torch

def generate_images(model_name, prompts_path, save_path, device='cuda:0', guidance_scale=7.5, image_size=512,
                    ddim_steps=100, num_samples=10, from_case=0):
    df = pd.read_csv(prompts_path)

    folder_path = f'{save_path}/{model_name}'
    os.makedirs(folder_path, exist_ok=True)

    for _, row in df.iterrows():
        prompt = [str(row.prompt)] * num_samples
        seed = row.evaluation_seed
        case_number = row.case_number
        if case_number < from_case:
            continue

        num_inference_steps = ddim_steps  # Number of denoising steps

        guidance_scale = guidance_scale  # Scale for classifier-free guidance

        generator = torch.manual_seed(seed)  # Seed generator to create the inital latent noise

        batch_size = len(prompt)
        with finetuner:
            pil_images = diffuser(prompt,
                                  img_size=image_size,
                                  n_steps=num_inference_steps,
                                  n_imgs=1,
                                  generator=generator,
                                  guidance_scale=guidance_scale
                                  )[0]

        # image = (image / 2 + 0.5).clamp(0, 1)
        # image = image.detach().cpu().permute(0, 2, 3, 1).numpy()
        # images = (image * 255).round().astype("uint8")
        # pil_images = [Image.fromarray(image) for image in images]
        for num, im in enumerate(pil_images):
            im.save(f"{folder_path}/{case_number}_{num}.png")

if __name__ == '__main__':
    parser = argparse.ArgumentParser(
        prog='generateImages',
        description='Generate Images using Diffusers Code')
    parser.add_argument('--model_name', help='name of model', type=str, required=True)
    parser.add_argument('--train_method', help='name of mode', type=str, required=True)
    parser.add_argument('--prompts_path', help='path to csv file with prompts', type=str, required=True)
    parser.add_argument('--save_path', help='folder where to save images', type=str, required=True)
    parser.add_argument('--device', help='cuda device to run on', type=str, required=False, default='cuda:0')
    parser.add_argument('--guidance_scale', help='guidance to run eval', type=float, required=False, default=7.5)
    parser.add_argument('--image_size', help='image size used to train', type=int, required=False, default=512)
    parser.add_argument('--from_case', help='continue generating from case_number', type=int, required=False, default=0)
    parser.add_argument('--num_samples', help='number of samples per prompt', type=int, required=False, default=1)
    parser.add_argument('--ddim_steps', help='ddim steps of inference used to train', type=int, required=False,
                        default=100)
    args = parser.parse_args()

    model_name = args.model_name
    prompts_path = args.prompts_path
    save_path = args.save_path
    device = args.device
    guidance_scale = args.guidance_scale
    image_size = args.image_size
    ddim_steps = args.ddim_steps
    num_samples = args.num_samples
    from_case = args.from_case
    train_method = args.train_method
    diffuser = StableDiffuser(scheduler='DDIM').to(device)

    finetuner = FineTunedModel(diffuser, train_method=train_method)
    esd_path = f'models/{model_name}.pt'
    finetuner.load_state_dict(torch.load(esd_path))

    generate_images(model_name, prompts_path, save_path, device=device,
                    guidance_scale=guidance_scale, image_size=image_size, ddim_steps=ddim_steps,
                    num_samples=num_samples, from_case=from_case)

    # python generate-images.py --model_name esd-vangogh_from_vangogh-xattn_1-epochs_200 --prompts_path data/vangogh_prompts.csv --save_path images/--device cuda:2

authors: chaoshuoZhang rohitgandikota

repo: rohitgandikota/erasing


text:
Doc UI not loading on servers

When attempting to load the Swagger documentation UI on the Core BB hosted on the servers it currently returns a blank page (see https://api.rokwire.illinois.edu/core/doc/ui/index.html). This is consistent across all server environments (dev, test, prod), however issue does not seem to occur when running locally. This issue also does not occur on the version hosted on our ROKMETRO servers.
After investigating with the browser "inspect" tool, we found that this page is making several requests that are failing with 404 errors.
GET https://api.rokwire.illinois.edu/core/doc/ui/swagger-ui.css net::ERR_ABORTED 404  index.html:68
GET https://api.rokwire.illinois.edu/core/doc/ui/swagger-ui-bundle.js net::ERR_ABORTED 404  index.html:69
GET https://api.rokwire.illinois.edu/core/doc/ui/swagger-ui-standalone-preset.js net::ERR_ABORTED 404  index.html:73
Uncaught ReferenceError: SwaggerUIBundle is not defined
    at window.onload (index.html:73:14)

We verified that on our servers these requests return successfully with content served by the http-swagger package.
I found a related issue on the http-swagger library: https://github.com/swaggo/http-swagger/issues/10

This issue seems to have resolved itself for now. This may have been the result of an issue with a specific deployment. Closing for now

repo: rokwire/core-building-block


text:
Cannot find plugin "karma-systemjs"

I'm getting this error:
06 10 2015 21:37:21.906:WARN [plugin]: Cannot find plugin "karma-systemjs".
  Did you forget to install it ?
  npm install karma-systemjs --save-dev
/Users/cosmin/.nvm/v0.12.4/lib/node_modules/karma/node_modules/di/lib/injector.js:9
      throw error('No provider for "' + name + '"!');
            ^
Error: No provider for "framework:systemjs"! (Resolving: framework:systemjs)
    at error (/Users/cosmin/.nvm/v0.12.4/lib/node_modules/karma/node_modules/di/lib/injector.js:22:68)
    at Object.parent.get (/Users/cosmin/.nvm/v0.12.4/lib/node_modules/karma/node_modules/di/lib/injector.js:9:13)
    at get (/Users/cosmin/.nvm/v0.12.4/lib/node_modules/karma/node_modules/di/lib/injector.js:54:19)
    at /Users/cosmin/.nvm/v0.12.4/lib/node_modules/karma/lib/server.js:137:20

"No I did not forget to install it"
I have this in package.json:
...
"devDependencies: {
   ...
   "karma-systemjs": "^0.8.0",
   ...
}
...

I have this in my karma.conf.js
plugins: ['karma-systemjs'],
frameworks: ['systemjs', 'mocha'],

and inside my proj_dir/node_modules/karma-systemjs/package.json I see this:
...
"name": "karma-systemjs",
"version": "0.8.0",
...

other details:
✔ ~
21:44 $ karma --version
Karma version: 0.13.10
✔ ~
21:44 $ node --version
v0.12.4
✔ ~
21:44 $ npm --version
2.10.1
✔ ~
21:44 $ uname -v
Darwin Kernel Version 14.5.0: Wed Jul 29 02:26:53 PDT 2015; root:xnu-2782.40.9~1/RELEASE_X86_64
( OSX 10.10.5 )

Going by the paths in your error (/Users/cosmin/.nvm/v0.12.4/lib/node_modules/karma) I'd guess that Karma is looking for plugins that have been installed globally, rather than locally.

yea that makes sense, looks like I need to use the locally installed executable ...
./node_modules/karma/bin/karma start works
pretty weird behaviour from karma, I'd assume the global CLI is expected to be used, it should be able to find locally installed plugins >:
anyways, thanks for your help and quick response

I am facing the same issue. It seems karma is looking for plugins locally but I am still getting this issue.
C:\osd\forms\node_modules\karma\node_modules\di\lib\injector.js:9
throw error('No provider for "' + name + '"!');
^
Error: No provider for "framework:systemjs"! (Resolving: framework:systemjs)
at error (C:\osd\forms\node_modules\karma\node_modules\di\lib\injector.js:22:68)
at Object.parent.get (C:\osd\forms\node_modules\karma\node_modules\di\lib\injector.js:9:13)
at [object Object].get (C:\osd\forms\node_modules\karma\node_modules\di\lib\injector.js:54:19)
at C:\osd\forms\node_modules\karma\lib\server.js:133:20
at Array.forEach (native)
at [object Object].Server._start (C:\osd\forms\node_modules\karma\lib\server.js:132:21)
at [object Object].invoke (C:\osd\forms\node_modules\karma\node_modules\di\lib\injector.js:75:15)
at [object Object].Server.start (C:\osd\forms\node_modules\karma\lib\server.js:97:18)
at Object.exports.run (C:\osd\forms\node_modules\karma\lib\cli.js:231:26)
at Object. (C:\osd\forms\node_modules\karma\bin\karma:3:23)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
at node.js:814:3

authors: kosz rolaveric vb8190

repo: rolaveric/karma-systemjs


text:
Allow configuring from host/prefix string

Q
A

Bug report?
no

Feature request?
yes

BC Break report?
no

RFC?
no

Currently the sections are registered using an array-like format, but for XML and .env files this is less then ideal.
Someone on the Symfony Slack made the following suggestion; Instead of using JSON the user can specify a URI path that is parsed into a host and prefix. But as this would disallow the usage of multiple tld's and require some major changes in the conflict resolving validator I am thinking of introducing a custom string syntax:
Eg. https://example.{tld;nl;nl,de}/prefix ({tld;nl;nl,de} defines the tld attribute with nl as default, and nl|de as accepted requirement).
Tip: As a small bonus this also makes it possible specify if https must be used.
What about other default? These only apply to routing so allow the route definition to provide additional defaults and requirements (no overwrites!)

Closed by #21

repo: rollerworks/app-sectioning


text:
Develop a testing strategy

Ideally, the following tests should exist:

reasonably high test coverage via unit-tests inside this repo
integration tests between lazyledger-app and optimint
run the simapp with optimint (see https://docs.cosmos.network/master/building-modules/simulator.html and https://github.com/cosmos/cosmos-sdk/blob/deaee531111fb4aad3ccabbfa6771f9a67ae42ce/simapp/app.go#L1)
integration tests between lazyledger-app and another very simple ORU app based on the Cosmos-SDK (using optimint under the hood)
spin up a small network with the LL main chain and two simple apps with their own dedicated clients

The first point is the only one that we needs immediate and continuous action. And I think we are on the right track for this. For the other points it is a bit too early but we should have them before the first testnet with ORU support.
We should definetely split this up into several issues. Point 5. alone is a bigger project on its own. I just wanted to jot this down for now. We could use this issue as a kind of meta issue to link between all relevant issues (and prs).

Closing this since testing has been added extensively to Rollkit

authors: Manav-Aggarwal liamsi

repo: rollkit/rollkit


text:
Clarification of correct TSV file for CC3M?

Hi! Your instructions to download CC3M state "Go to https://ai.google.com/research/ConceptualCaptions/download and press download That's a 500MB tsv file"
However, when I go to that URL, there are three download buttons:

Your instructions then state to modify cc3m.tsv but none of the three downloaded files are named cc3m.tsv:

Training -> Train_GCC-training.tsv (564 MB)
Validation -> Validation_GCC-1.1.0-Validation.tsv (2.6 MB)
Image Labels -> Image_Labels_Subset_Train_GCC-Labels-training.tsv (1.3 GB)

The instructions do state that the file should be ~500 MB, which roughly matches the file obtained by downloading the training split (Train_GCC-training.tsv)
Could you please clarify how to obtain the correct cc3m.tsv file?

Good question, I don't have the answer. Maybe you can download all 3 files and see which one have the right number of sample and the right columns?
You may compare against https://huggingface.co/datasets/pixparse/cc3m-wds

Hi! Your instructions to download CC3M state "Go to https://ai.google.com/research/ConceptualCaptions/download and press download That's a 500MB tsv file"
However, when I go to that URL, there are three download buttons:

Your instructions then state to modify cc3m.tsv but none of the three downloaded files are named cc3m.tsv:

Training -> Train_GCC-training.tsv (564 MB)
Validation -> Validation_GCC-1.1.0-Validation.tsv (2.6 MB)
Image Labels -> Image_Labels_Subset_Train_GCC-Labels-training.tsv (1.3 GB)

The instructions do state that the file should be ~500 MB, which roughly matches the file obtained by downloading the training split (Train_GCC-training.tsv)
Could you please clarify how to obtain the correct cc3m.tsv file?

@RylanSchaeffer Hi! I have the same problem, have you solved it?

I switched to a different dataset.


text:
"if" is matched

Thanks. It's unfortunately not easy to negate something in the RE flavors used by Ctags so the "method" patterns currently also match if, while and for.

I know the reason.My code like this:
if() {
}
could be matched.
But like this:
if () {
}
could not be matched.

I know the reason.My code like this:
if() {
}

could be matched.
But like this:
if () {
}

could not be matched.

if doesn't seem to be matched anymore. Closing this issue.

authors: romainl zjkdragon

repo: romainl/ctags-patterns-for-javascript


text:
[BUG] Query using link field, with fetch_links=False

Describe the bug
In the docs, it says the following:
Search by linked documents fields
If the fetch_links parameter is set to True, search by linked documents fields is available.
By field of the direct link:
houses = await House.find(
    House.door.height == 2,
    fetch_links=True
).to_list()

By list of links:
houses = await House.find(
    House.windows.x > 10,
    fetch_links=True
).to_list()

Search by id of the linked documents works using the following syntax:
houses = await House.find(
    House.door.id == "DOOR_ID_HERE"
).to_list()

It works the same way with fetch_links equal to True and False and for find_many and find_one methods.
Expected behavior
From the documentation (specifically the last sentence there in bold), it is implied that I can do the following and get a result
houses = await House.find(
    House.windows.x > 10,
    fetch_links=False
).to_list()

However, I tried it and it just returns an empty list.
So I think that as a first step the documentation should be updated to specify that in order to query on fields of linked docs you have to set fetch_links=True.
And as a feature request, I would like to be able to query on the linked object's field's without actually fetching it, if that makes sense

Hi! Sorry for the confusion. The line It works the same way with fetch_links equal to True and False and for find_many and find_one methods pertained to using only ids. I will update the documentation to make it clearer.
Unfortunately, it is impossible to make this feature available without fetching in the current approach I am using. When it doesn't fetch links, it uses find queries. When it does fetch, it employs aggregation pipelines under the hood. To enable searching by fields in the linked documents for all cases, I have to use aggregation pipelines consistently. However, this can potentially reduce performance.
Could you please explain your use case? I can consider how to add new functionality or introduce a new flag to enable such searching for cases like yours.

Thanks for the update :).
Yeah, I would Imagine that's it's not a trivial thing to implement, especially without hurting performance in the general case.
In this particular case I have a Person Document - that has in it some fields like name, and email, and also a Person can have a manager - who is also a person, so it's a link.
I want to be able to get a person based on a manager's name for example.
In this case I guess it could be somewhat problematic, because from what I've seen if I pass fetch_links=True it will also fetch them recursively - so I would get the manager of a manager of a manager etc. - which sounds very inefficient.
In general I think it could be a useful feature in some cases to be able to query a document based on fields of links, without actually fetching the full link. How easy or difficuly it is to implement - that's another question, I'm guessing it could get pretty complicated. I guess the deeper issue here is that mongo doesn't have JOIN as a core concept

Sorry for the late reply,
Yes, searching by the ID of linked docs should work even without prefetching.
Regarding recursive fetching - I don't think fetch_links=True will reduce performance too much. It will fetch 2 layers deep only and then stop. And even if I make a solution for this without actual fetching, it will work the same way on the database side using the same aggregation pipeline, but with a projection to remove links. The difference is - the Python app will parse a few more objects. If you don't fetch hundreds of objects, it will have no effect on performance.

Great! I wasn't aware that there is a limit to the fetch depth.

authors: alex-linx roman-right

repo: roman-right/beanie


text:
Support for WebPack.

We should apply WebPack to our project.

https://webpack.github.io/

The following comments comes from #261(closed).

Directory stucture

css, scss, image, javascript
webpack entry, output files

Build command for only client or do with server

repo: romandev/absolute


text:
E5601: Cannot close window, only floating window would remain

If I'm inside a function where nvim-treesitter-context gets activated, than I'm getting this error message:
E5601: Cannot close window, only floating window would remain

So everytime when I want to quit, I need to move out of the nesting in order to close neovim.

Can't reproduce, can you provide the steps you take to get the message?

I'm busy currentl I'll try to create a minimal init.vim if I've got the time. But until that I'll close this issue temporary (if it's fine for you).

I can reproduce it. Open any source file, move around until the context floating window shows up. Execute :close, the error message shows. Then move around until the context floating window disappears, :close works as expected then.

Can't reproduce, with the following steps:

 echo 'static
 void my_function(
       int lines,
       char *text
       ) {

 }' > test.c

nvim test.c
5<c-e>:q<CR>

Oh ok, I see. The problem is you're using :close to quit, but the correct command would be :quit. There is nothing we can do here to allow for the behavior you're looking for. I'd suggest using :quit (or ZZ, or ZQ) instead.

:quit (or ZZ, or ZQ) behaves just like close. Still see the error.

Can't reproduce, please provide an example file with clear steps and a minimal config.

Ok, this bug doesn't appear for me anymore. I have absolutely no idea, why it doesn't happen... but since @ipod825 has this iccue, I'll reopen this issue.

I think I know how to reproduce it.
Try :quit when two or more tabs are open.

https://user-images.githubusercontent.com/50843046/114859828-89d14200-9deb-11eb-8d37-25dab2b8106b.mp4

I think I know how to reproduce it.
Try :quit when two or more tabs are open.

Yes! It happens for me now!

I can reproduce that. Unfortunately, I don't see a way to fix your use-case, here is the documentation for :quit:
Quit the current window.  Quit Vim if this is the last window.

:quit operation order seems to be first close the window, then quit vim. In other words, it's also doing a :close and will suffer the same problems as a :close. From our end, there is no way to know in advance that the user is going to issue a :quit command so we have no way to close the floating window in advance. Mind you, if I have 2 tabpages open and do :quit, vim doesn't exit; it only closes one of the tabpages. All that to say, if what you want is to quit vim, the actual command you should be using would be :qall. Unless someone as another proposition to fix the issue, I would close this and add a mention on the readme.

@romgrk How about providing a wrapper function or command of :quit?
I have no knowledge about the internals of nvim-treesitter-context, but at least it should know if the context window is present or not.
If the context window exists and the original window is the last window of the current tab (of course, except for the context window), winnr('$') will be 2 and the wrapper can close both the context and original windows. Otherwise, it could just invoke :quit.
At the moment, one workaround for users is to use :tabclose when it's needed. Caveats I'm aware are 1. it always closes all the windows in the current tab and 2. it fails if the current tab is the only tab.

I'm not opposed, but can you elaborate on why :qall doesn't satisfy your use-case?

Thanks for considering it.
That's because using :quit, I want to close only the current window (which might be the last window in the current tab), not the whole nvim instance.
I thought that a unified wrapper could eliminate the need for manually switching between :quit and :tabclose, but at the same time, I'm a bit worried that it might complicate such a basic operation (closing a window).
By the way, it looks that there is a related issue for this matter in the neovim project: https://github.com/neovim/neovim/issues/11440

If it's an upstream issue I'd rather fix it upstream, I've opened https://github.com/neovim/neovim/pull/14387.

The context is saved in Buffer, so :qa cannot close it directly

I did a workaround for this by prepending G to the mapping of my quit function: ex:
// before
nmap <leader>w :q!

// after
nmap <leader>w G:q!

I'm also using this, but I'm rather pressing G on my own.

Fyi, this comment suggests a trick for closing all floating windows, which you can use in your mapping.

This is fixed in Neovim 0.7

repo: romgrk/nvim-treesitter-context


text:
Running as root is not recommended Issue

Hi,
followed the install tutorial on my pi but when executing jupyter it stops with the error message about root issues.
[I 11:55:37.449 NotebookApp] Writing notebook server cookie secret to /root/.local/share/jupyter/runtime/notebook_cookie_secret [W 11:55:37.525 NotebookApp] WARNING: The notebook server is listening on all IP addresses and not using encryption. This is not recommended. [C 11:55:37.558 NotebookApp] Running as root is not recommended. Use --allow-root to bypass.
any idea what I am doing wrong?

You're not doing anything wrong. Running an unprotected Jupiter notebook on
a network is generally not a good idea, hence the warnings, but running one
on a Pi inside a docker container is likely to be safe enough.
On 17 Jun 2017 14:01, "othreed" notifications@github.com wrote:

Hi,
followed the install tutorial on my pi but when executing jupyter it stops
with the error message about root issues.
[I 11:55:37.449 NotebookApp] Writing notebook server cookie secret to
/root/.local/share/jupyter/runtime/notebook_cookie_secret [W 11:55:37.525
NotebookApp] WARNING: The notebook server is listening on all IP addresses
and not using encryption. This is not recommended. [C 11:55:37.558
NotebookApp] Running as root is not recommended. Use --allow-root to bypass.
any idea what I am doing wrong?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/romilly/rpi-docker-tensorflow/issues/2, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAJHPoVfZeeFKZsMS7pNR3quRNB8Etu4ks5sE8FZgaJpZM4N9NUq
.

somehow it goes back to the shell after putting out the error about:
Running as root is not recommended. Use --allow-root to bypass.
I cannot access the URL via webbrowser. This is why I thought it is mandatory to run it not as root... but I cannot get it to work

I'll spin up a pi tomorrow and investigate.
On 17 Jun 2017 17:58, "othreed" notifications@github.com wrote:

somehow it goes back to the shell after putting out the error about:
Running as root is not recommended. Use --allow-root to bypass.
I cannot access the URL via webbrowser. This is why I thought it is
mandatory to run it not as root... but I cannot get it to work
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/romilly/rpi-docker-tensorflow/issues/2#issuecomment-309226958,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJHPvcid7zFM0swL74rTrrdGxhZ8WTaks5sFAXTgaJpZM4N9NUq
.

I've pushed an (untested) fix to github. If you have a chance to test it
before I do, please let me know if it works :)
On 17 June 2017 at 18:19, Romilly Cocking romilly.cocking@gmail.com wrote:

I'll spin up a pi tomorrow and investigate.
On 17 Jun 2017 17:58, "othreed" notifications@github.com wrote:

somehow it goes back to the shell after putting out the error about:
Running as root is not recommended. Use --allow-root to bypass.
I cannot access the URL via webbrowser. This is why I thought it is
mandatory to run it not as root... but I cannot get it to work
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/romilly/rpi-docker-tensorflow/issues/2#issuecomment-309226958,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJHPvcid7zFM0swL74rTrrdGxhZ8WTaks5sFAXTgaJpZM4N9NUq
.

--
personal:@romillyc work:@rareblog skype:romilly.cocking web:
http://blog.rareschool.com/

Thank you for the quick fix. It works
WOW

authors: othreed romilly

repo: romilly/rpi-docker-tensorflow


text:
功能建议:希望添加各站点的自动签到功能

以前一直用的ppt，直到发现了这个插件，ppt就丢一边去了，希望能够自动签到，免得有时候忘记断签真的很伤心

暂时不会考虑签到功能
https://github.com/ronggang/PT-Plugin-Plus/issues/13

自动签到功能很实用啊，希望可以增加自动签到功能

自动签到真的很实用，希望大佬可以添加，谢谢

authors: JackZhangCHN Rhilip Warm-rain icaobo

repo: ronggang/PT-Plugin-Plus


text:
Pager crashes when searching for non-existent pattern under certain conditions

When searching for a pattern that does not appear in the pager output, after having just searched for a pattern, pager crashes.
To replicate the issue, construct a random matrix and pipe into pager:
rand(100, 100) |> pager
Once in pager mode, search for a pattern that you see (e.g. / 0.7). All instances of that pattern will be highlighted, and something like (match 1 of 1464)   41% will appear on the bottom right. If you hit escape at this point, there is no issue. However, if you search for another pattern and that pattern does not exist (e.g. /.123456), while the search results from the previous search are still shown, pager will crash with the following stacktrace:
ERROR: BoundsError: attempt to access 0-element Vector{Tuple{Int64, Int64, Int64}} at index [1]
Stacktrace:
  [1] getindex
    @ ./array.jl:801 [inlined]
  [2] _move_view_to_match!
    @ ~/.julia/packages/TerminalPager/C06ZN/src/search.jl:109 [inlined]
  [3] _pager_event_process!(pagerd::TerminalPager.Pager)
    @ TerminalPager ~/.julia/packages/TerminalPager/C06ZN/src/pager.jl:313
  [4] _pager!(term::REPL.Terminals.TTYTerminal, str::String; freeze_columns::Int64, freeze_rows::Int64, change_freeze::Bool, hashelp::Bool)
    @ TerminalPager ~/.julia/packages/TerminalPager/C06ZN/src/pager.jl:130
  [5] _pager!
    @ ~/.julia/packages/TerminalPager/C06ZN/src/pager.jl:80 [inlined]
  [6] _pager(str::String; kwargs::Base.Iterators.Pairs{Union{}, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
    @ TerminalPager ~/.julia/packages/TerminalPager/C06ZN/src/pager.jl:59
  [7] _pager
    @ ~/.julia/packages/TerminalPager/C06ZN/src/pager.jl:53 [inlined]
  [8] #pager#28
    @ ~/.julia/packages/TerminalPager/C06ZN/src/TerminalPager.jl:49 [inlined]
  [9] pager
    @ ~/.julia/packages/TerminalPager/C06ZN/src/TerminalPager.jl:49 [inlined]
 [10] #pager#27
    @ ~/.julia/packages/TerminalPager/C06ZN/src/TerminalPager.jl:46 [inlined]
 [11] pager
    @ ~/.julia/packages/TerminalPager/C06ZN/src/TerminalPager.jl:45 [inlined]
 [12] |>(x::Matrix{Float64}, f::typeof(pager))
    @ Base ./operators.jl:858
 [13] top-level scope
    @ REPL[6]:1

julia> versioninfo()
Julia Version 1.6.0
Commit f9720dc2eb (2021-03-24 12:55 UTC)
Platform Info:
  OS: Linux (x86_64-pc-linux-gnu)
  CPU: AMD Ryzen 7 PRO 4750U with Radeon Graphics
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-11.0.1 (ORCJIT, znver2)

Hi @EarthGoddessDude
Good catch. It should be fixed in main. Can you please test?

@ronisbr, my pleasure. Looks good on main, no more crash in that scenario.

authors: EarthGoddessDude ronisbr


text:
🛑 TROJAN 🇩🇪 Germany DEH 1 is down

In ad6ad37, TROJAN 🇩🇪 Germany DEH 1 (https://det-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇩🇪 Germany DEH 1 is back up in a9f5a3e.

repo: roosterkid/opentunnel-status-server


text:
🛑 TROJAN 🇭🇰 Hong Kong HKE 1 is down

In 57b4689, TROJAN 🇭🇰 Hong Kong HKE 1 (https://hkt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇭🇰 Hong Kong HKE 1 is back up in 5997dd8.


text:
🛑 TROJAN 🇺🇸 United States USO 1 is down

In 2da604f, TROJAN 🇺🇸 United States USO 1 (https://ust-2.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇺🇸 United States USO 1 is back up in 604b24d.


text:
🛑 TROJAN 🇬🇧 United Kingdom UKM 1 is down

In 8ecc6a7, TROJAN 🇬🇧 United Kingdom UKM 1 (https://ukt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇬🇧 United Kingdom UKM 1 is back up in b7c4ba0.


text:
🛑 TROJAN 🇸🇬 Singapore SGP 1 is down

In a5d59d6, TROJAN 🇸🇬 Singapore SGP 1 (https://sgt-2.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇸🇬 Singapore SGP 1 is back up in 1efc313.


text:
🛑 V2RAY 🇸🇬 Singapore SGO 5 is down

In 2f8114f, V2RAY 🇸🇬 Singapore SGO 5 (https://sgv-6.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇸🇬 Singapore SGO 5 is back up in 106a93d.


text:
🛑 SSH 🇮🇩 Indonesia IDA 1 is down

In 67cba3d, SSH 🇮🇩 Indonesia IDA 1 (http://ids-2.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇮🇩 Indonesia IDA 1 is back up in 5b166e3.


text:
🛑 TROJAN 🇬🇧 United Kingdom UKO 2 is down

In 112dc53, TROJAN 🇬🇧 United Kingdom UKO 2 (https://ukt-2.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇬🇧 United Kingdom UKO 2 is back up in bb415d6.


text:
🛑 SSH 🇮🇩 Indonesia IDA 1 is down

In bf278cc, SSH 🇮🇩 Indonesia IDA 1 (http://ids-2.optnl.com:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇮🇩 Indonesia IDA 1 is back up in 1356e0a.


text:
🛑 TROJAN 🇳🇱 Netherlands NLB 1 is down

In 1ebcbfa, TROJAN 🇳🇱 Netherlands NLB 1 (https://nlt-1.optnl.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇳🇱 Netherlands NLB 1 is back up in 2e44cb9.


text:
🛑 TROJAN 🇬🇧 United Kingdom UKO 2 is down

In 9d66ec9, TROJAN 🇬🇧 United Kingdom UKO 2 (https://ukt-2.optnl.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇬🇧 United Kingdom UKO 2 is back up in 5f36523.


text:
🛑 TROJAN 🇺🇸 United States USO 1 is down

In ad77a98, TROJAN 🇺🇸 United States USO 1 (https://ust-2.optnl.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇺🇸 United States USO 1 is back up in 8c6902f.


text:
🛑 XRAY 🇮🇩 Indonesia IDA 1 is down

In d967e39, XRAY 🇮🇩 Indonesia IDA 1 (https://idx-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇮🇩 Indonesia IDA 1 is back up in abce7a5.


text:
🛑 TROJAN 🇩🇪 Germany DEO 1 is down

In e69ea93, TROJAN 🇩🇪 Germany DEO 1 (https://det-1.optnl.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇩🇪 Germany DEO 1 is back up in 07c1301.


text:
🛑 V2RAY 🇱🇻 Latvia LVH 1 is down

In 9958f5d, V2RAY 🇱🇻 Latvia LVH 1 (https://lvv-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇱🇻 Latvia LVH 1 is back up in b7d4e14.


text:
🛑 V2RAY 🇺🇸 United States USF 1 is down

In 6a4ad75, V2RAY 🇺🇸 United States USF 1 (https://usv-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇺🇸 United States USF 1 is back up in c497b3c.


text:
🛑 TROJAN 🇩🇪 Germany DEO 1 is down

In 26968a6, TROJAN 🇩🇪 Germany DEO 1 (https://det-1.optnl.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇩🇪 Germany DEO 1 is back up in 4636db5.


text:
🛑 XRAY 🇺🇸 United States USF 1 is down

In 446a7c9, XRAY 🇺🇸 United States USF 1 (https://usx-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇺🇸 United States USF 1 is back up in 72480b1.


text:
🛑 TROJAN 🇸🇬 Singapore SGA 1 is down

In bfeb8b3, TROJAN 🇸🇬 Singapore SGA 1 (https://sgt-3.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇸🇬 Singapore SGA 1 is back up in 6da856b.


text:
🛑 TROJAN 🇭🇰 Hong Kong HKE 1 is down

In 4d707b8, TROJAN 🇭🇰 Hong Kong HKE 1 (https://hkt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇭🇰 Hong Kong HKE 1 is back up in f5c5482.


text:
🛑 TROJAN 🇺🇸 United States USF 1 is down

In e1b97ed, TROJAN 🇺🇸 United States USF 1 (https://ust-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇺🇸 United States USF 1 is back up in 2f3a3ae.


text:
🛑 TROJAN 🇬🇧 United Kingdom UKO 2 is down

In 075adff, TROJAN 🇬🇧 United Kingdom UKO 2 (https://ukt-2.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇬🇧 United Kingdom UKO 2 is back up in 893d692.


text:
办『加拿大』谢里丹学院文凭证书「Sheridan毕业证成绩单(1954292140微信/q)],学历认证谢里丹学院毕业证书%原版↑制作,办理Sheridan大学留学回国人员证明,谢里丹学院国外学历学位认证Sheridan Colleg

办『加拿大』谢里丹学院文凭证书【qq：1954292140 微信：1954292140】学历文凭！使馆认证！留学回国人员证明！录取通知书！Offer！在读证明！网上存档永久可查！
◆办理真实使馆认证（即留学回国人员证明，不成功不收费）
◆办理degree，Transcripts（一对一服务包括毕业院长签字,专业课程,学位类型,专业或教育领域,以及毕业日期.不要忽视这些细节.这两份文件同样重要!毕业证成绩单文凭留信网学历认证！）
◆办理各国各大学（世界名校一对一专业服务，可全程监控跟踪进度）
◆全套服务：毕业证、成绩单真实使馆认证、真实教育部认证。让您回国发展信心十足！
◆可以提供钢印、水印、烫金、激光防伪、凹凸版、最新版的毕业证、百分之百让您绝对满意、设计，印刷;毕业证、成绩单，真实大使馆教育部认证，速度快。
办理毕业证加拿大学历文凭/微信1954292140「Sheridan毕业证成绩单(1954292140微信/q)],学历认证谢里丹学院毕业证书%原版↑制作,办理Sheridan大学留学回国人员证明,谢里丹学院国外学历学位认证Sheridan Colleg

Hi @srj275400080,
It looks like the issue template is missing from this issue. Please take a look at the Contribution Guidelines, which will tell you exactly what your ticket has to contain in order to be processable.
Please do not use the issue tracker for personal support requests. Use Roots Discourse to ask the Roots community for help, or hire someone from the community.

repo: roots/sage


text:
Bump node-sass dependency to 4.13.1

node-sass ~4.9.4 will fail on certain environments. This will simply bump the version to node-sass@latest (4.13.1) which corrects the issue.
Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (72)

I saw the approval a few times. I can't merge this.

Can we get this merged? Really painful having to manually bump this dependency

+1! Now node-sass@4.14.0! Older versions won't install on WSL.

tracking here: #2466

authors: johnpaulmedina matthewlukedesign retlehs strarsis


text:
webui does not come up again after deinstall/reinstall

I had a running node 1.7.0 which I updated to 1.8.0.
All worked fine to some point and I had a fully synced node with webui up and running.
For some reason I needed to reinstall everything (at the same day). afterwards the webgui (of the synced node) did not show the correct values anmore, but hung insiting on that bitcoin was off and lnd not synced. So I stiwtched to the menu and deintsalled the webui, restarted and installed the webui again. Now my node is synced, btc and lnd both synced and running, redis in the process list, but my webui shows an error only -- 403 Forbidden, which seems that nginx (which I assume is a reverse proxy only) cannot get to any info provided ny nodejs/redis (or whatever).
I already restarted nginx, redis and rebootet - no change. my btc node and lnd both look fine for me.
How to restart the webui without rewriting the complete sd-card?

Hi @jagottsicher
Can you try to disable & enable the API & webUI again?

Should work with 1.9.0

authors: cstenglein jagottsicher

repo: rootzoll/raspiblitz


text:
Option to ignore file tags

I write tasks in my daily notes which are built from a template that includes file tags in the frontmatter:
---
tags: daily_note, journal
---

- [ ] Do stuff #in-progress
- [ ] Do more stuff

As a result, every task will automatically get these tags applied which makes the "Untagged" column of a board unable to be used.

In the above screenshot, I would expect there to be "Do more stuff" in the "Untagged" column, but its not there because of the file tags of "daily_note" and "journal".
If I remove the file tags, this does work, but I would prefer if I could keep the file tags and have the option to ignore them when applying filters

Goal here is to add an option to the board settings that allows a user to toggle whether column filters ignore file tags

Would adding an 'Other Tags' column get you what you are after.  This should include tasks which do have tags other than the ones being used for columns on the board. ...although I am guessing that the issue here is that it will also include the 'Do stuff' card as this also has other tags on it!
I do plan to re-visit tag based columns at some point as there are some other useful cases which could sensibly supported so great to have this suggestion!  It will be a while tho as my current drag-and-drop work has quite a bit of work yet to be done.
Thank you :)

Would adding an 'Other Tags' column get you what you are after. This should include tasks which do have tags other than the ones being used for columns on the board. ...although I am guessing that the issue here is that it will also include the 'Do stuff' card as this also has other tags on it!

Yes, I tried this and the #in-progress tag was also included in the "Other Tags" column.

I do plan to re-visit tag based columns at some point as there are some other useful cases which could sensibly supported so great to have this suggestion! It will be a while tho as my current drag-and-drop work has quite a bit of work yet to be done.

No worries!  I cut the file tags from the frontmatter for now and it works great.  Had to adjust some dataview scripts, but thats not a big deal.  Looking forward to drag and drop! Thank you!

authors: roovo scottTomaszewski

repo: roovo/obsidian-card-board


text:
Update pyserial dependency to install it with rosdep

This allows rosdep to find the correct serial package and install it.

Thanks for the update!

authors: evenator mvoellmy


text:
Depth image encoding is hard-coded

The current implementation appears to hard-code the expected image encoding of the depth image:
https://github.com/ros-industrial/industrial_reconstruction/blob/2cf137d2941be6425bc4908e70c0cc1a2fc34c63/industrial_reconstruction/industrial_reconstruction/industrial_reconstruction.py#L288-L288
it doesn't do this for the regular RGB images:
https://github.com/ros-industrial/industrial_reconstruction/blob/2cf137d2941be6425bc4908e70c0cc1a2fc34c63/industrial_reconstruction/industrial_reconstruction/industrial_reconstruction.py#L289-L289
Looking at various drivers, there are two main 'types' of depth images:

16-bit unsigned with depth in mm (16UC1)
32-bit float with depth in m (32FC1)

At least in ROS 1, the depth_image_proc/convert_metric nodelet can be used to convert between the two types.
The hard-coded 16UC1 (and the existence of the depth_scale parameter) implies the first is expected and has been used when developing industrial_reconstruction. The code as-is is incompatible with the second type.
Would it be desirable to remove the hard-coding and rely on what is set in sensor_msgs::msgs::Image::encoding field instead?

Would it be desirable to remove the hard-coding and rely on what is set in sensor_msgs::msgs::Image::encoding field instead?

Yes, this would definitely be preferable. Upon initial creation of this node I had some issues trying to do that, so I just ran with what would work for the initial application. It sounds like you and  @Aashish-TUD have an application using different camera encodings than what I've used in the past, if you guys have a working change for that I would definitely want to merge that in.

authors: gavanderhoorn marrts