FAIL to start "moveit_servo" (ROS2 Foxy)

I am trying with ROS2 Foxy on TB3 with OpenManipulator-X, and followed the instructions in emanual for all setup.
However, when I try to teleoperate the arm, but error: FAIL to start FAIL to start "moveit_servo"
T1: ros2 launch turtlebot3_manipulation_bringup hardware.launch.py   ==> No error
T2: ros2 launch turtlebot3_manipulation_moveit_config servo.launch.py ==> No error
T3: ros2 run turtlebot3_manipulation_teleop turtlebot3_manipulation_teleop ==> ERROR!!!
T3: ros2 service list ==> Can get /servo_server...

Why this ERROR happen? Anything I missed out?

It seems to me that the issue is that it can't find the moveit_servo package. Try reinstalling the moveit2 package from source from moveit2 and give it another shot.

It seems to me that the issue is that it can't find the moveit_servo package. Try reinstalling the moveit2 package from source from moveit2 and give it another shot.

I cannot regenerate this problem anymore because after I reinstall the micro SD card with either ROS2 Foxy or ROS2 Humble, I cannot bring up the TB3 with OpenManipulator-X at all! It keeps showing "[ros2_control_node-1] [ERROR] [DynamixelSDKWrapper] [TxRxResult] There is no status packet!", similar like the issue in https://github.com/ROBOTIS-GIT/turtlebot3_manipulation/issues/63! But there is no update on that issue!!!

@eRobotclub  I'm curious if Dynamixel and OpenCR are communicating properly. When you turn on your OpenCR, do the manipulator and both wheels remain stationary due to torque when touched?

@eRobotclub I'm curious if Dynamixel and OpenCR are communicating properly. When you turn on your OpenCR, do the manipulator and both wheels remain stationary due to torque when touched?

Yes, when power on the OpenCR, all the Dynamixel on wheels and manipulator are TORQUE ON.
And if I upload the OpenCR firmware for waffle pi (without manipulation) to the robot, I can bringup and teleoperate TB3 with no problem, therefore the USB connection between Raspberry Pi and OpenCR is OK.
And if I use Androind IDE to search connected Dynamixels on OpenCR, I can found all ID 1, 2, 11, 12, 13, 14, 15 motors, therefore the connection between Dynamixels and OpeCR also no problem.
Furthermore, I am not the only one facing the same problem: https://github.com/ROBOTIS-GIT/turtlebot3_manipulation/issues/63
so maybe some issue after ROS2 updated? Or issue on OpenCR firmware for ROS2? I have no idea how to fix this...

@eRobotclub I understand your difficulties. I tried to reproduce this issue using ROS2 Humble version, but I was unable to replicate it. First, I reinstalled Humble on both Turtlebot3 and the remote PC from scratch following the e-manual. When I executed the command "ros2 launch turtlebot3_manipulation_bringup hardware.launch.py" on the Turtlebot, the "[DynamixelSDKWrapper] [TxRxResult] There is no status packet!" log appeared only once initially and did not persist.
The ROS2 firmware for OpenCR (OPENCR_MODEL=turtlebot3_manipulation) seems to be working correctly. Try deleting the opencr_update folder in your home directory and update it again. Here are my logs:
Regarding the issue you mentioned initially, it can occur if your Turtlebot and remote PC are not properly connected. Ensure that the ROS_DOMAIN_ID is the same on both devices. Additionally, 5G WiFi may not work well for this connection, so I recommend using a hotspot to connect them.

turtlebot@robotis:~$ ros2 launch turtlebot3_manipulation_bringup hardware.launch.py
[INFO] [launch]: All log files can be found below /home/turtlebot/.ros/log/2024-06-12-18-59-51-966397-robotis-2872
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [ros2_control_node-1]: process started with pid [2875]
[INFO] [robot_state_publisher-2]: process started with pid [2877]
[INFO] [spawner-3]: process started with pid [2879]
[INFO] [ld08_driver-4]: process started with pid [2881]
[robot_state_publisher-2] Link base_link had 8 children
[robot_state_publisher-2] Link link1 had 1 children
[robot_state_publisher-2] Link link2 had 1 children
[robot_state_publisher-2] Link link3 had 1 children
[robot_state_publisher-2] Link link4 had 1 children
[robot_state_publisher-2] Link link5 had 3 children
[robot_state_publisher-2] Link end_effector_link had 0 children
[robot_state_publisher-2] Link gripper_left_link had 0 children
[robot_state_publisher-2] Link gripper_right_link had 0 children
[robot_state_publisher-2] Link camera_link had 1 children
[robot_state_publisher-2] Link camera_rgb_frame had 1 children
[robot_state_publisher-2] Link camera_rgb_optical_frame had 0 children
[robot_state_publisher-2] Link caster_back_left_link had 0 children
[robot_state_publisher-2] Link caster_back_right_link had 0 children
[robot_state_publisher-2] Link imu_link had 0 children
[robot_state_publisher-2] Link base_scan had 0 children
[robot_state_publisher-2] Link wheel_left_link had 0 children
[robot_state_publisher-2] Link wheel_right_link had 0 children
[robot_state_publisher-2] [INFO] [1718186395.156581212] [robot_state_publisher]: got segment base_footprint
[robot_state_publisher-2] [INFO] [1718186395.157400842] [robot_state_publisher]: got segment base_link
[robot_state_publisher-2] [INFO] [1718186395.157539045] [robot_state_publisher]: got segment base_scan
[robot_state_publisher-2] [INFO] [1718186395.157578675] [robot_state_publisher]: got segment camera_link
[robot_state_publisher-2] [INFO] [1718186395.157611045] [robot_state_publisher]: got segment camera_rgb_frame
[robot_state_publisher-2] [INFO] [1718186395.157642249] [robot_state_publisher]: got segment camera_rgb_optical_frame
[robot_state_publisher-2] [INFO] [1718186395.157672490] [robot_state_publisher]: got segment caster_back_left_link
[robot_state_publisher-2] [INFO] [1718186395.157705231] [robot_state_publisher]: got segment caster_back_right_link
[robot_state_publisher-2] [INFO] [1718186395.157734101] [robot_state_publisher]: got segment end_effector_link
[robot_state_publisher-2] [INFO] [1718186395.157762768] [robot_state_publisher]: got segment gripper_left_link
[robot_state_publisher-2] [INFO] [1718186395.157790508] [robot_state_publisher]: got segment gripper_right_link
[robot_state_publisher-2] [INFO] [1718186395.157819286] [robot_state_publisher]: got segment imu_link
[robot_state_publisher-2] [INFO] [1718186395.157846749] [robot_state_publisher]: got segment link1
[robot_state_publisher-2] [INFO] [1718186395.157878490] [robot_state_publisher]: got segment link2
[robot_state_publisher-2] [INFO] [1718186395.158123268] [robot_state_publisher]: got segment link3
[robot_state_publisher-2] [INFO] [1718186395.158234064] [robot_state_publisher]: got segment link4
[robot_state_publisher-2] [INFO] [1718186395.158272342] [robot_state_publisher]: got segment link5
[robot_state_publisher-2] [INFO] [1718186395.158303693] [robot_state_publisher]: got segment wheel_left_link
[robot_state_publisher-2] [INFO] [1718186395.158339212] [robot_state_publisher]: got segment wheel_right_link
[ros2_control_node-1] [INFO] [1718186395.231406582] [resource_manager]: Loading hardware 'TurtleBot3ManipulationSystem'
[ros2_control_node-1] [INFO] [1718186395.259100564] [resource_manager]: Initialize hardware 'TurtleBot3ManipulationSystem'
[ros2_control_node-1] [INFO] [1718186395.264583175] [turtlebot3_manipulation]: Succeeded to open port
[ros2_control_node-1] [INFO] [1718186395.272265916] [turtlebot3_manipulation]: Succeeded to set baudrate
[ros2_control_node-1] [INFO] [1718186395.287146323] [turtlebot3_manipulation]: OpenCR Model Number 20480
[ros2_control_node-1] [INFO] [1718186395.288756342] [turtlebot3_manipulation]: Connected manipulator
[ros2_control_node-1] [INFO] [1718186395.292072842] [turtlebot3_manipulation]: Connected wheels
[ros2_control_node-1] [INFO] [1718186395.292479175] [resource_manager]: Successful initialization of hardware 'TurtleBot3ManipulationSystem'
[ros2_control_node-1] [INFO] [1718186395.293335064] [resource_manager]: 'configure' hardware 'TurtleBot3ManipulationSystem'
[ros2_control_node-1] [INFO] [1718186395.293428471] [resource_manager]: Successful 'configure' of hardware 'TurtleBot3ManipulationSystem'
[ros2_control_node-1] [INFO] [1718186395.293470471] [resource_manager]: 'activate' hardware 'TurtleBot3ManipulationSystem'
[ros2_control_node-1] [INFO] [1718186395.293492712] [turtlebot3_manipulation]: Ready for start
[ros2_control_node-1] [INFO] [1718186395.307727619] [turtlebot3_manipulation]: Wait for IMU re-calibration
[ros2_control_node-1] [ERROR] [DynamixelSDKWrapper] [TxRxResult] There is no status packet!
[ld08_driver-4] /dev/ttyACM0    OpenCR Virtual ComPort in FS Mode
[ld08_driver-4] /dev/ttyUSB0    CP2102 USB to UART Bridge Controller
[ld08_driver-4] FOUND LDS-02
[ld08_driver-4] LDS-02 started successfully
[spawner-3] [INFO] [1718186395.898352230] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' services to be available
[spawner-3] [INFO] [1718186397.924276284] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' services to be available
[ros2_control_node-1] [INFO] [1718186398.342340192] [turtlebot3_manipulation]: Joints and wheels torque ON
[ros2_control_node-1] [INFO] [1718186398.354094395] [turtlebot3_manipulation]: Set profile acceleration and velocity to joints
[ros2_control_node-1] [INFO] [1718186398.392128951] [turtlebot3_manipulation]: Set profile acceleration and velocity to gripper
[ros2_control_node-1] [INFO] [1718186398.416131080] [turtlebot3_manipulation]: Set goal current value to gripper
[ros2_control_node-1] [INFO] [1718186398.436146414] [turtlebot3_manipulation]: System starting
[ros2_control_node-1] [INFO] [1718186398.438163414] [resource_manager]: Successful 'activate' of hardware 'TurtleBot3ManipulationSystem'
[ros2_control_node-1] [INFO] [1718186398.457623654] [controller_manager]: update rate is 100 Hz
[ros2_control_node-1] [INFO] [1718186398.459564654] [controller_manager]: RT kernel is recommended for better performance
[ros2_control_node-1] [INFO] [1718186398.460149284] [turtlebot3_manipulation]: Start to read wheels and manipulator states
[ros2_control_node-1] [INFO] [1718186398.462682562] [turtlebot3_manipulation]: Start to write wheels and manipulator commands
[ros2_control_node-1] [INFO] [1718186398.601921228] [controller_manager]: Loading controller 'joint_state_broadcaster'
[spawner-3] [INFO] [1718186398.676516006] [spawner_joint_state_broadcaster]: Loaded joint_state_broadcaster
[ros2_control_node-1] [INFO] [1718186398.680561747] [controller_manager]: Configuring controller 'joint_state_broadcaster'
[ros2_control_node-1] [INFO] [1718186398.680897414] [joint_state_broadcaster]: 'joints' or 'interfaces' parameter is empty. All available state interfaces will be published
[spawner-3] [INFO] [1718186398.780882043] [spawner_joint_state_broadcaster]: Configured and activated joint_state_broadcaster
[INFO] [spawner-3]: process has finished cleanly [pid 2879]
[INFO] [spawner-5]: process started with pid [2924]
[INFO] [spawner-6]: process started with pid [2926]
[INFO] [spawner-7]: process started with pid [2928]
[INFO] [spawner-8]: process started with pid [2930]
[ros2_control_node-1] [INFO] [1718186400.788323116] [controller_manager]: Loading controller 'diff_drive_controller'
[ros2_control_node-1] [INFO] [1718186401.067272783] [controller_manager]: Loading controller 'gripper_controller'
[spawner-8] [INFO] [1718186401.202576653] [spawner_diff_drive_controller]: Loaded diff_drive_controller
[ros2_control_node-1] [INFO] [1718186401.207497523] [controller_manager]: Loading controller 'arm_controller'
[spawner-5] [INFO] [1718186401.350191060] [spawner_gripper_controller]: Loaded gripper_controller
[ros2_control_node-1] [INFO] [1718186401.371746227] [joint_trajectory_controller.interpolation_methods]: No interpolation method parameter was given. Using the default, VARIABLE_DEGREE_SPLINE.
[ros2_control_node-1] [INFO] [1718186401.405127560] [controller_manager]: Configuring controller 'diff_drive_controller'
[ros2_control_node-1] [INFO] [1718186401.425924671] [controller_manager]: Configuring controller 'gripper_controller'
[ros2_control_node-1] [INFO] [1718186401.426241264] [gripper_controller]: Action status changes will be monitored at 20Hz.
[spawner-6] [INFO] [1718186401.496726764] [spawner_arm_controller]: Loaded arm_controller
[ros2_control_node-1] [INFO] [1718186401.529735690] [controller_manager]: Configuring controller 'arm_controller'
[ros2_control_node-1] [INFO] [1718186401.530103819] [arm_controller]: No specific joint names are used for command interfaces. Using 'joints' parameter.
[ros2_control_node-1] [INFO] [1718186401.530328023] [arm_controller]: Command interfaces are [position] and state interfaces are [position velocity].
[ros2_control_node-1] [INFO] [1718186401.530429301] [joint_trajectory_controller.interpolation_methods]: No interpolation method parameter was given. Using the default, VARIABLE_DEGREE_SPLINE.
[ros2_control_node-1] [INFO] [1718186401.530453282] [arm_controller]: Using 'splines' interpolation method.
[ros2_control_node-1] [INFO] [1718186401.531888986] [arm_controller]: Controller state will be published at 200.00 Hz.
[spawner-5] [INFO] [1718186401.532653560] [spawner_gripper_controller]: Configured and activated gripper_controller
[ros2_control_node-1] [INFO] [1718186401.534674486] [arm_controller]: Action status changes will be monitored at 20.00 Hz.
[spawner-8] [INFO] [1718186401.659235041] [spawner_diff_drive_controller]: Configured and activated diff_drive_controller
[ros2_control_node-1] [INFO] [1718186401.761258949] [controller_manager]: Loading controller 'imu_broadcaster'
[spawner-6] [INFO] [1718186401.764257134] [spawner_arm_controller]: Configured and activated arm_controller
[spawner-7] [INFO] [1718186401.961028597] [spawner_imu_broadcaster]: Loaded imu_broadcaster
[ros2_control_node-1] [INFO] [1718186401.971154189] [controller_manager]: Configuring controller 'imu_broadcaster'
[INFO] [spawner-8]: process has finished cleanly [pid 2930]
[spawner-7] [INFO] [1718186402.086606837] [spawner_imu_broadcaster]: Configured and activated imu_broadcaster
[INFO] [spawner-5]: process has finished cleanly [pid 2924]
[INFO] [spawner-6]: process has finished cleanly [pid 2926]
[INFO] [spawner-7]: process has finished cleanly [pid 2928]

Also, when you updated the firmware, did it update successfully like the log below?

@sunghowoo
I burn again the Ubuntu Server 22.04 to the micro SD card again~
Then setup and install ROS2 Humble with following commands:
sudo nano /etc/netplan/50-cloud-init.yaml
sudo nano /etc/apt/apt.conf.d/20auto-upgrades
systemctl mask systemd-networkd-wait-online.service
sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
reboot
locale
sudo apt update && sudo apt install locales
sudo locale-gen en_US en_US.UTF-8
sudo update-locale LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8
export LANG=en_US.UTF-8
locale
sudo apt install software-properties-common
sudo add-apt-repository universe
sudo apt update && sudo apt install curl -y
sudo curl -sSL https://raw.githubusercontent.com/ros/rosdistro/master/ros.key -o /usr/share/keyrings/ros-archive-keyring.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/ros-archive-keyring.gpg] http://packages.ros.org/ros2/ubuntu $(. /etc/os-release && echo $UB>
sudo apt update
sudo apt upgrade -y
sudo apt install ros-humble-desktop
sudo apt install ros-humble-ros-base
sudo apt install ros-dev-tools
source /opt/ros/humble/setup.bash
sudo apt install python3-argcomplete python3-colcon-common-extensions libboost-system-dev build-essential
sudo apt install ros-humble-hls-lfcd-lds-driver
sudo apt install ros-humble-turtlebot3-msgs
sudo apt install ros-humble-dynamixel-sdk
sudo apt install libudev-dev
sudo reboot
mkdir -p ~/turtlebot3_ws/src && cd ~/turtlebot3_ws/src
git clone -b humble-devel https://github.com/ROBOTIS-GIT/turtlebot3.git
git clone -b ros2-devel https://github.com/ROBOTIS-GIT/ld08_driver.git
git clone -b humble-devel https://github.com/ROBOTIS-GIT/turtlebot3_manipulation.git
cd ~/turtlebot3_ws/src/turtlebot3
rm -r turtlebot3_cartographer turtlebot3_navigation2
echo 'source /opt/ros/humble/setup.bash' >> ~/.bashrc
source ~/.bashrc
cd ~/turtlebot3_ws/
sudo rosdep init
rosdep update
rosdep install --from-paths src --ignore-src -r -y
source ~/.bashrc
colcon build --symlink-install --parallel-workers 1
echo 'source ~/turtlebot3_ws/install/setup.bash' >> ~/.bashrc
source ~/.bashrc
sudo udevadm control --reload-rules
sudo udevadm trigger
source ~/.bashrc
echo 'export LDS_MODEL=LDS-01' >> ~/.bashrc
source ~/.bashrc
sudo dpkg --add-architecture armhf
sudo apt update
sudo apt install libc6:armhf
cd ~
export OPENCR_MODEL=turtlebot3_manipulation
rm -rf ./opencr_update.tar.bz2
wget https://github.com/ROBOTIS-GIT/OpenCR-Binaries/raw/master/turtlebot3/ROS2/latest/opencr_update.tar.bz2
tar -xvf opencr_update.tar.bz2
cd ./opencr_update
./update.sh $OPENCR_PORT $OPENCR_MODEL.opencrcd ./opencr_update
cd ~
source ~/.bashrc
ros2 launch turtlebot3_manipulation_bringup hardware.launch.py
I used rosdep to install some package because if just following the instruction in emanual, some instruction such as hardware-interface is not installed!
Then I get the error when bring up:
ubuntu@ubuntu:~/opencr_update$ ./update.sh $OPENCR_PORT $OPENCR_MODEL.opencr
aarch64
arm
OpenCR Update Start..
opencr_ld_shell ver 1.0.0
opencr_ld_main
[  ] file name          : turtlebot3_manipulation.opencr
[  ] file size          : 136 KB
[  ] fw_name            : turtlebot3_manipulation
[  ] fw_ver             : V230127R1
[OK] Open port          : /dev/ttyACM0
[  ]
[  ] Board Name         : OpenCR R1.0
[  ] Board Ver          : 0x17020800
[  ] Board Rev          : 0x00000000
[OK] flash_erase        : 1.13s
[OK] flash_write        : 1.33s
[OK] CRC Check          : DA11C4 DA11C4 , 0.005000 sec
[OK] Download
[OK] jump_to_fw
ubuntu@ubuntu:~/opencr_update$ cd ~
ubuntu@ubuntu:~$ ros2 launch turtlebot3_manipulation_bringup hardware.launch.py
[INFO] [launch]: All log files can be found below /home/ubuntu/.ros/log/2024-06-18-02-00-37-238487-ubuntu-9035
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [ros2_control_node-1]: process started with pid [9038]
[INFO] [robot_state_publisher-2]: process started with pid [9040]
[INFO] [spawner-3]: process started with pid [9042]
[INFO] [hlds_laser_publisher-4]: process started with pid [9044]
[hlds_laser_publisher-4] [INFO] [1718676039.585755544] [hlds_laser_publisher]: Init hlds_laser_publisher Node Main
[hlds_laser_publisher-4] [INFO] [1718676039.588282191] [hlds_laser_publisher]: port : /dev/ttyUSB0 frame_id : base_scan
[robot_state_publisher-2] [INFO] [1718676039.627838379] [robot_state_publisher]: got segment base_footprint
[robot_state_publisher-2] [INFO] [1718676039.628313690] [robot_state_publisher]: got segment base_link
[robot_state_publisher-2] [INFO] [1718676039.628383671] [robot_state_publisher]: got segment base_scan
[robot_state_publisher-2] [INFO] [1718676039.628416745] [robot_state_publisher]: got segment camera_link
[robot_state_publisher-2] [INFO] [1718676039.628444096] [robot_state_publisher]: got segment camera_rgb_frame
[robot_state_publisher-2] [INFO] [1718676039.628471596] [robot_state_publisher]: got segment camera_rgb_optical_frame
[robot_state_publisher-2] [INFO] [1718676039.628497744] [robot_state_publisher]: got segment caster_back_left_link
[robot_state_publisher-2] [INFO] [1718676039.628523688] [robot_state_publisher]: got segment caster_back_right_link
[robot_state_publisher-2] [INFO] [1718676039.628548892] [robot_state_publisher]: got segment end_effector_link
[robot_state_publisher-2] [INFO] [1718676039.628573466] [robot_state_publisher]: got segment gripper_left_link
[robot_state_publisher-2] [INFO] [1718676039.628723705] [robot_state_publisher]: got segment gripper_right_link
[robot_state_publisher-2] [INFO] [1718676039.628757038] [robot_state_publisher]: got segment imu_link
[robot_state_publisher-2] [INFO] [1718676039.628782205] [robot_state_publisher]: got segment link1
[robot_state_publisher-2] [INFO] [1718676039.628806556] [robot_state_publisher]: got segment link2
[robot_state_publisher-2] [INFO] [1718676039.628832038] [robot_state_publisher]: got segment link3
[robot_state_publisher-2] [INFO] [1718676039.628857315] [robot_state_publisher]: got segment link4
[robot_state_publisher-2] [INFO] [1718676039.628884778] [robot_state_publisher]: got segment link5
[robot_state_publisher-2] [INFO] [1718676039.628909370] [robot_state_publisher]: got segment wheel_left_link
[robot_state_publisher-2] [INFO] [1718676039.628935296] [robot_state_publisher]: got segment wheel_right_link
[ros2_control_node-1] [WARN] [1718676039.656358821] [controller_manager]: [Deprecated] Passing the robot description parameter directly to the control_manager node is deprecated. Use '~/robot_description' topic from 'robot_state_publisher' instead.
[ros2_control_node-1] [INFO] [1718676039.658232380] [resource_manager]: Loading hardware 'TurtleBot3ManipulationSystem'
[ros2_control_node-1] [INFO] [1718676039.661474910] [resource_manager]: Initialize hardware 'TurtleBot3ManipulationSystem'
[ros2_control_node-1] [INFO] [1718676039.666624684] [turtlebot3_manipulation]: Succeeded to open port
[ros2_control_node-1] [INFO] [1718676039.674296420] [turtlebot3_manipulation]: Succeeded to set baudrate
[ros2_control_node-1] [INFO] [1718676039.704707884] [turtlebot3_manipulation]: OpenCR Model Number 20480
[ros2_control_node-1] [ERROR] [DynamixelSDKWrapper] [TxRxResult] There is no status packet!
[ros2_control_node-1] [FATAL] [1718676039.739130871] [turtlebot3_manipulation]: Not connected manipulator
[ros2_control_node-1] [INFO] [1718676039.739246944] [resource_manager]: Failed to initialize hardware 'TurtleBot3ManipulationSystem'
[ros2_control_node-1] [WARN] [1718676039.739273296] [resource_manager]: System hardware component 'TurtleBot3ManipulationSystem' from plugin 'turtlebot3_manipulation_hardware/TurtleBot3ManipulationSystemHardware' failed to initialize.
[ros2_control_node-1] terminate called after throwing an instance of 'std::runtime_error'
[ros2_control_node-1]   what():  Wrong state or command interface configuration.
[ros2_control_node-1] missing state interfaces:
[ros2_control_node-1] ' wheel_left_joint/position '     ' wheel_left_joint/velocity '   ' wheel_right_joint/position '  ' wheel_right_joint/velocity '  ' joint1/position '     ' joint1/velocity '     ' joint2/position '     ' joint2/velocity '     ' joint3/position '     ' joint3/velocity '     ' joint4/position '     ' joint4/velocity '     ' gripper_left_joint/position ' ' gripper_left_joint/velocity ' ' gripper_right_joint/position '        ' gripper_right_joint/velocity '        ' imu/orientation.x '   ' imu/orientation.y '   ' imu/orientation.z '   ' imu/orientation.w '   ' imu/angular_velocity.x '      ' imu/angular_velocity.y '      ' imu/angular_velocity.z '      ' imu/linear_acceleration.x '   ' imu/linear_acceleration.y '   ' imu/linear_acceleration.z '   ' battery/voltage '     ' battery/percentage '  ' battery/design_capacity '     ' battery/present '
[ros2_control_node-1] missing command interfaces:
[ros2_control_node-1] ' wheel_left_joint/velocity '     ' wheel_right_joint/velocity '  ' joint1/position '     ' joint2/position '     ' joint3/position '     ' joint4/position '     ' gripper_left_joint/position ' ' gripper_right_joint/position '
[ros2_control_node-1] Stack trace (most recent call last):
[ros2_control_node-1] #15   Object "/usr/lib/aarch64-linux-gnu/ld-linux-aarch64.so.1", at 0xffffffffffffffff, in
[ros2_control_node-1] #14   Object "/opt/ros/humble/lib/controller_manager/ros2_control_node", at 0xaaaabec02c6f, in
[ros2_control_node-1] #13   Object "/usr/lib/aarch64-linux-gnu/libc.so.6", at 0xffff928374cb, in __libc_start_main
[ros2_control_node-1] #12   Object "/usr/lib/aarch64-linux-gnu/libc.so.6", at 0xffff928373fb, in
[ros2_control_node-1] #11   Object "/opt/ros/humble/lib/controller_manager/ros2_control_node", at 0xaaaabec02767, in
[ros2_control_node-1] #10   Object "/opt/ros/humble/lib/libcontroller_manager.so", at 0xffff92ee24cb, in controller_manager::ControllerManager::ControllerManager(std::shared_ptrrclcpp::Executor, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, rclcpp::NodeOptions const&)
[ros2_control_node-1] #9    Object "/opt/ros/humble/lib/libcontroller_manager.so", at 0xffff92ede5f7, in controller_manager::ControllerManager::init_resource_manager(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)
[ros2_control_node-1] #8    Object "/opt/ros/humble/lib/libhardware_interface.so", at 0xffff926a71bb, in hardware_interface::ResourceManager::load_urdf(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, bool, bool)
[ros2_control_node-1] #7    Object "/opt/ros/humble/lib/libhardware_interface.so", at 0xffff926a8be7, in hardware_interface::ResourceManager::validate_storage(std::vector<hardware_interface::HardwareInfo, std::allocator<hardware_interface::HardwareInfo> > const&) const
[ros2_control_node-1] #6    Object "/usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.30", at 0xffff92a92e03, in __cxa_throw
[ros2_control_node-1] #5    Object "/usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.30", at 0xffff92a92b1f, in std::terminate()
[ros2_control_node-1] #4    Object "/usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.30", at 0xffff92a92abb, in
[ros2_control_node-1] #3    Object "/usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.30", at 0xffff92a962db, in __gnu_cxx::__verbose_terminate_handler()
[ros2_control_node-1] #2    Object "/usr/lib/aarch64-linux-gnu/libc.so.6", at 0xffff9283712f, in abort
[ros2_control_node-1] #1    Object "/usr/lib/aarch64-linux-gnu/libc.so.6", at 0xffff9284a67b, in raise
[ros2_control_node-1] #0    Object "/usr/lib/aarch64-linux-gnu/libc.so.6", at 0xffff9288f200, in
[ros2_control_node-1] Aborted (Signal sent by tkill() 9038 1000)
[ERROR] [ros2_control_node-1]: process has died [pid 9038, exit code -6, cmd '/opt/ros/humble/lib/controller_manager/ros2_control_node --ros-args --params-file /tmp/launch_params_xbkucuxp --params-file /home/ubuntu/turtlebot3_ws/install/turtlebot3_manipulation_bringup/share/turtlebot3_manipulation_bringup/config/hardware_controller_manager.yaml -r ~/cmd_vel_unstamped:=cmd_vel -r ~/odom:=odom'].
[spawner-3] [INFO] [1718676042.839215436] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-3] [INFO] [1718676044.902652257] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-3] [INFO] [1718676046.963765878] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-3] [INFO] [1718676049.024242211] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-3] [ERROR] [1718676050.878423562] [spawner_joint_state_broadcaster]: Controller manager not available
[ERROR] [spawner-3]: process has died [pid 9042, exit code 1, cmd '/opt/ros/humble/lib/controller_manager/spawner joint_state_broadcaster --controller-manager /controller_manager --ros-args'].
[INFO] [spawner-5]: process started with pid [9086]
[INFO] [spawner-6]: process started with pid [9088]
[INFO] [spawner-7]: process started with pid [9090]
[INFO] [spawner-8]: process started with pid [9092]
[spawner-7] [INFO] [1718676055.083555305] [spawner_imu_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-8] [INFO] [1718676055.146858214] [spawner_diff_drive_controller]: Waiting for '/controller_manager' node to exist
[spawner-5] [INFO] [1718676055.164711388] [spawner_gripper_controller]: Waiting for '/controller_manager' node to exist
[spawner-6] [INFO] [1718676055.235554405] [spawner_arm_controller]: Waiting for '/controller_manager' node to exist
[spawner-7] [INFO] [1718676057.145886860] [spawner_imu_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-8] [INFO] [1718676057.207541042] [spawner_diff_drive_controller]: Waiting for '/controller_manager' node to exist
[spawner-5] [INFO] [1718676057.209342546] [spawner_gripper_controller]: Waiting for '/controller_manager' node to exist
[spawner-6] [INFO] [1718676057.295828958] [spawner_arm_controller]: Waiting for '/controller_manager' node to exist
[spawner-7] [INFO] [1718676059.206192213] [spawner_imu_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-5] [INFO] [1718676059.266002261] [spawner_gripper_controller]: Waiting for '/controller_manager' node to exist
[spawner-8] [INFO] [1718676059.266002575] [spawner_diff_drive_controller]: Waiting for '/controller_manager' node to exist
[spawner-6] [INFO] [1718676059.355159022] [spawner_arm_controller]: Waiting for '/controller_manager' node to exist
[spawner-7] [INFO] [1718676061.265914796] [spawner_imu_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-8] [INFO] [1718676061.327309812] [spawner_diff_drive_controller]: Waiting for '/controller_manager' node to exist
[spawner-5] [INFO] [1718676061.327309275] [spawner_gripper_controller]: Waiting for '/controller_manager' node to exist
[spawner-6] [INFO] [1718676061.414674551] [spawner_arm_controller]: Waiting for '/controller_manager' node to exist
[spawner-7] [ERROR] [1718676063.115611313] [spawner_imu_broadcaster]: Controller manager not available
[spawner-5] [ERROR] [1718676063.179945936] [spawner_gripper_controller]: Controller manager not available
[spawner-8] [ERROR] [1718676063.179945899] [spawner_diff_drive_controller]: Controller manager not available
[spawner-6] [ERROR] [1718676063.268298574] [spawner_arm_controller]: Controller manager not available
[ERROR] [spawner-7]: process has died [pid 9090, exit code 1, cmd '/opt/ros/humble/lib/controller_manager/spawner imu_broadcaster --ros-args'].
[ERROR] [spawner-5]: process has died [pid 9086, exit code 1, cmd '/opt/ros/humble/lib/controller_manager/spawner gripper_controller --ros-args'].
[ERROR] [spawner-8]: process has died [pid 9092, exit code 1, cmd '/opt/ros/humble/lib/controller_manager/spawner diff_drive_controller -c /controller_manager --ros-args'].
[ERROR] [spawner-6]: process has died [pid 9088, exit code 1, cmd '/opt/ros/humble/lib/controller_manager/spawner arm_controller --ros-args'].

I don't know why it show "[ros2_control_node-1] [FATAL] [1718676039.739130871] [turtlebot3_manipulation]: Not connected manipulator"?
I use Arduino IDE to scan on OpenCR, I get all 7 Dynamixels...

This issue occurs with the latest version of Dynamixel, and it has been confirmed that it can be resolved by using the Dynamixel Wizard to change the Return Delay Time of all motors from 250 ms to 0 ms.


Image scan has detect several vulnerabilites

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
Trivy image scanner has detect several vulnerabilites:
trivy image ghcr.io/arvatoaws-labs/traefik:2.6.1
2022-02-21T16:55:10.707+0100	INFO	Detected OS: alpine
2022-02-21T16:55:10.707+0100	INFO	Detecting Alpine vulnerabilities...
2022-02-21T16:55:10.708+0100	INFO	Number of language-specific files: 1
2022-02-21T16:55:10.708+0100	INFO	Detecting gobinary vulnerabilities...

ghcr.io/arvatoaws-labs/traefik:2.6.1 (alpine 3.14.3)
====================================================
Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)

usr/local/bin/traefik (gobinary)
================================
Total: 4 (UNKNOWN: 2, LOW: 0, MEDIUM: 0, HIGH: 1, CRITICAL: 1)

+--------------------------------------+------------------+----------+-------------------+------------------------+---------------------------------------+
|               LIBRARY                | VULNERABILITY ID | SEVERITY | INSTALLED VERSION |     FIXED VERSION      |                 TITLE                 |
+--------------------------------------+------------------+----------+-------------------+------------------------+---------------------------------------+
| github.com/containerd/containerd     | CVE-2021-43816   | CRITICAL | v1.5.8            | 1.5.9                  | containerd: Unprivileged pod          |
|                                      |                  |          |                   |                        | may bind mount any privileged         |
|                                      |                  |          |                   |                        | regular file on disk...               |
|                                      |                  |          |                   |                        | -->avd.aquasec.com/nvd/cve-2021-43816 |
+--------------------------------------+------------------+----------+-------------------+------------------------+---------------------------------------+
| github.com/hashicorp/consul          | CVE-2021-41805   | HIGH     | v1.10.3           | 1.8.17, 1.9.11, 1.10.4 | Incorrect Authorization               |
|                                      |                  |          |                   |                        | -->avd.aquasec.com/nvd/cve-2021-41805 |
+--------------------------------------+------------------+----------+-------------------+------------------------+---------------------------------------+
| github.com/opencontainers/image-spec | GMS-2021-101     | UNKNOWN  | v1.0.1            | 1.0.2                  | Clarify `mediaType` handling          |
+--------------------------------------+------------------+          +-------------------+------------------------+---------------------------------------+
| golang.org/x/text                    | CVE-2021-38561   |          | v0.3.6            | 0.3.7                  | -->avd.aquasec.com/nvd/cve-2021-38561 |
+--------------------------------------+------------------+----------+-------------------+------------------------+---------------------------------------+

What did you see instead?
"CRITICAL" and "HIGH" vulnerabilities
What version of Traefik are you using?
2.6.1
What is your environment & configuration?
AWS EKS 1.21
Traefik 2.6.1

Hello @albertschwarzkopf,
Thanks for your interest in Traefik,
As mentioned in other issues (https://github.com/traefik/traefik-helm-chart/issues/555 and https://github.com/traefik/traefik-library-image/issues/21), we are not affected by those CVEs. The same applies to the github.com/opencontainers/image-spec and golang.org/x/text ones. Those reports are false positive.
Therefore, we will close this issue accordingly.


[fix] Fixing SQL parsing issue

CATEGORY
Choose one

[x] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
This PR fixes an issue with parsing SQL where iterating over the identifiers associated with a sqlparser IdentifierList yields a Token (as opposed to a TokenList) resulting in the following error:
builtins:AttributeError: 'Token' object has no attribute 'tokens'

Note I worked somewhat extensively with sqlparse on an unrelated project and there's probably some merit in restructuring some of this logic in the future.
TEST PLAN
CI.
REVIEWERS
to: @michellethomas @mistercrunch

Do you have input SQL that failed before and succeeds not that we could add as unit test here?:
https://github.com/apache/incubator-superset/blob/master/tests/sql_parse_tests.py

@mistercrunch I added a test for the specific problem. It's somewhat of a corner case but a user was using a SQL keyword as an alias within a multi WITH statement and so for a statement of the form ..., <keyword> AS ... the <keyword>  is a Token (where the ttype is Token.Keyword) rather than a TokenList.

Codecov Report

Merging #7374 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master   #7374      +/-   ##
=========================================
+ Coverage   64.89%   64.9%   +<.01%
=========================================
  Files         428     428
  Lines       20979   20981       +2
  Branches     2337    2337
=========================================
+ Hits        13615   13617       +2
  Misses       7240    7240
  Partials      124     124

Impacted Files
Coverage Δ

superset/sql_parse.py
99.14% <100%> (+0.01%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4fe152d...a2e4fc1. Read the comment docs.

I'm not sure if related but linking the issue https://github.com/apache/incubator-superset/issues/7400

@mistercrunch are you ok with approving this PR?

I just merged a PR from @betodealmeida touching this code. This LGTM but this code is opaque so it's hard to review...


Workflow without LBaaS

Hi there,
I installed Deis but without LBaaS. Details why are here: https://github.com/Waziup/Platform/issues/32
So my deis-router is configured with Service type = NodePort.
I configured an ingress controller though, that allows me to configure an app on a URL such as myapp.mysite.com
http://kubernetes.io/docs/user-guide/ingress/
Currently when I push an app:
git push deis master

It returns an url that is not valid (says http://leader-windmill.waziup.io/).
I have to create an ingress resource myself to route the application:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: leader-windmill
  namespace: leader-windmill
spec:
  rules:
  - host: leader-windmill.waziup.io
    http:
      paths:
      - path: /
         backend:
          serviceName: leader-windmill
          servicePort: 80

Is it possible that deis uses my ingress controller automatically?

Currently no without any changes as the deis assumes deis router is the one through which traffic come and goes. For more discussion on it see https://github.com/deis/router/issues/292. But i am pretty sure it is easy to add that extra piece of code in the controller to create an ingress object after the successful deploy.


Feature request: show consequences of deleting an org

At the moment, it's easy to accidentally delete private domains by deleting the org that owns them--operators intuitively except that deleting an org will delete its spaces and apps, but forget that deleting an org deletes associated domains. I'm making this claim because this has happened on my team a few times in the last few months alone 😓.
It would be helpful for the confirmation prompt for cf delete-org to be more explicit about what's going to be deleted, for example: "This will delete the private domains foo.com, baz.com". Even changing the current "delete the org and everything associated with it" to "delete the org and its associated spaces, apps, services, private domains, ..." would be more clear.

Seconding @jmcarp, I think because private domains are so much "less managed" than spaces/apps, it can be easy to miss that they are there. A reminder/cue would be very helpful given the user behavior I've observed. Thank y'all!

Related suggestion: the cf delete-shared-domain command should warn when there are existing routes, and request confirmation for deleting them before actually performing the deletion. Like cf delete-org, it's easy for operators to incorrectly predict the effect of cf delete-shared-domain - see this explanation of 18F site downtime from December for an example.

@brittag About cf delete-shared-domain, it currently displays:
D:\Users\koperd\Downloads\bin>cf delete-shared-domain my-domain.com
Deleting domain mydomain.com as admin...

This domain is shared across all orgs.
Deleting it will remove all associated routes, and will make any app with this domain unreachable.
Are you sure you want to delete the domain mydomain.com? >

It already warns about removing existing routes and asks confirmation?

@dkoper I am not sure that's entirely clear. I would suggest changing the language to:
This action impacts all orgs using this domain. Deleting it will remove associated routes and make any app with this domain, in any org, unreachable. Are you sure you want to delete the domain mydomain.com?

Could cf delete-shared-domain list the associated routes as well?
This action impacts all orgs using this domain. Deleting it will remove associated routes and make any app with this domain, in any org, unreachable. (Routes to be deleted: x.example.com, y.example.com, z.example.com) Are you sure you want to delete the domain mydomain.com?

I'd like to squeeze in a message improvement now as listing impacted resources requires more development & testing work that will have to compete with other feature work and issues.
About @wslack's message, apps can have multiple routes so deleting one doesn't necessarily make all apps inaccessible. Such a message would be worrying when you're trying to change your apps from one domain to another and just added new routes to your apps. OK if I add "could"?
This action impacts all orgs using this domain. Deleting it will remove associated routes and could
make any app with this domain, in any org, unreachable. Are you sure you want to delete the
domain mydomain.com?

And for delete-org, would (for now) the following do?
Really delete the org myorg, incl. its spaces, apps, services, routes and private domains? [yN]:

I notice this issue was mentioned in the release notes for v6.26.0!

delete-org and delete-shared-domain now display in more detail what else gets deleted in their confirmation messages. (#1082)

First of all: Huzzah!
Second: Should we be closing this issue?

@mogul I'm fine with closing it if you are.
I left it open as we only did the "quick" solution of improving the static message of what other (type of) resources would be deleted (see my comment above), and not actually producing a full list of resource names. Which would be a lot more work on this command.

Closing this issue as complete as the CLI now warns users with a more verbose output when deleting an org Really delete the org banana, including its spaces, apps, service instances, routes, private domains and space-scoped service brokers? .
Please feel free to open a new issue if you have comments/feedback. Thanks.


Cargo build does not update access times for existing files

Was looking into #8 and #9 when I seemed to discover an issue with access times on Windows.
After making sure that NtfsDisableLastAccessUpdate was disabled I did the following.
cargo clean
cargo build
// Now all build artifacts are the latest version, and that only.
cargo sweep -s
cargo build
// Now all build artifacts "should" have been accessed and thus be newer than the timestamp file
cargo sweep -f
// Now everything get removed :(

Will look into this more in the coming days when I have the time as this is quite the serious issue for the windows platform.

Have been really busy but now have tried this on OSX as well. Here we run in to the exact same issue. This very aggressive cleaning (i.e only keeping lastest version) points out an issue with the general approach of access/modified times where Cargo can completely jump over reading many of the needed build files. And with unmodified access times there is no way to distinguish what is being used or not. One possible "solution" is to do something as discussed in #6 in which only certain build files are cleaned keeping the partial results intact and therefor the build times fast. Otherwise we might simply have to wait for the stabilization of --build-plan to do this properly.

I would love to see an implementation based on the build-plan. If using build-plan is difficult, now would be the best time to request changes. If having used it the build-plan is exactly what you need that would be a big push for Cargo to go ahead and stabilize it.

I hope to manage to allocate some time to work on a nightly-only implementation using build-plan during the holidays and see what I can come up with. Would be nice to get it stabilized since I think it could solve the problems outlined above.

Same issue here on Linux. Given that it does remove files even if they are somewhat needed for next compilations, that makes the tool pointless for me : I might as well just cargo clean.
Couldn't we identify which artifacts are built for the current version of each library present in the Cargo.lock and remove any of these that is not present there ? This would allow for an easy cleaning of all the library versions that were updated and most likely won't be downgraded.

@Ten0 thats exactly what the build-plan is for: avoiding reimplementing all the cargo internals that are used to determine exactly what files an artifact depends on, recursively.


chore(deps): update angular-eslint monorepo to v16 (major)

This PR contains the following updates:

Package
Type
Update
Change

@angular-eslint/builder
devDependencies
major
~15.2.0 -> ~16.0.0

@angular-eslint/eslint-plugin
devDependencies
major
~15.2.0 -> ~16.0.0

@angular-eslint/eslint-plugin-template
devDependencies
major
~15.2.0 -> ~16.0.0

@angular-eslint/schematics
devDependencies
major
~15.2.0 -> ~16.0.0

@angular-eslint/template-parser
devDependencies
major
~15.2.0 -> ~16.0.0

Release Notes

angular-eslint/angular-eslint (@angular-eslint/builder)
v16.0.3
Compare Source
Bug Fixes

update nrwl monorepo to v16.2.2 (#1391) (9f140e6)

v16.0.2
Compare Source
Bug Fixes

update nrwl monorepo to v16.1.3 (#1371) (323d2c9)

v16.0.1
Compare Source
Note: Version bump only for package @angular-eslint/builder
v16.0.0
Compare Source
Note: Version bump only for package @angular-eslint/builder
15.2.1 (2023-02-10)
Note: Version bump only for package @angular-eslint/builder

angular-eslint/angular-eslint (@angular-eslint/eslint-plugin)
v16.0.3
Compare Source
Bug Fixes

update typescript-eslint packages to v5.59.7 (#1392) (cf40e34)

v16.0.2
Compare Source
Note: Version bump only for package @angular-eslint/eslint-plugin
v16.0.1
Compare Source
Note: Version bump only for package @angular-eslint/eslint-plugin
v16.0.0
Compare Source
Note: Version bump only for package @angular-eslint/eslint-plugin
15.2.1 (2023-02-10)
Bug Fixes

update typescript-eslint packages to v5.48.2 (#1278) (69d56a7)

angular-eslint/angular-eslint (@angular-eslint/eslint-plugin-template)
v16.0.3
Compare Source
Bug Fixes

update typescript-eslint packages to v5.59.7 (#1392) (cf40e34)

v16.0.2
Compare Source
Note: Version bump only for package @angular-eslint/eslint-plugin-template
v16.0.1
Compare Source
Note: Version bump only for package @angular-eslint/eslint-plugin-template
v16.0.0
Compare Source
Note: Version bump only for package @angular-eslint/eslint-plugin-template
15.2.1 (2023-02-10)
Bug Fixes

eslint-plugin-template: [i18n] handle ng-template properly (#1257) (7b0877d)
update typescript-eslint packages to v5.48.2 (#1278) (69d56a7)

angular-eslint/angular-eslint (@angular-eslint/schematics)
v16.0.3
Compare Source
Bug Fixes

update nrwl monorepo to v16.2.2 (#1391) (9f140e6)
update typescript-eslint packages to v5.59.7 (#1392) (cf40e34)

v16.0.2
Compare Source
Bug Fixes

update dependency eslint to v8.40.0 (#1341) (44f4233)
update nrwl monorepo to v16.1.3 (#1371) (323d2c9)

v16.0.1
Compare Source
Bug Fixes

schematics: ensure placeholder schema for convert-tslint-to-eslint is copied to dist (3c6f377)

v16.0.0
Compare Source
Features

update to Angular 16 stable (9b0138d)

15.2.1 (2023-02-10)
Bug Fixes

update dependency eslint to v8.32.0 (#1276) (15d2e23)
update dependency eslint to v8.33.0 (#1292) (bd82b42)
update typescript-eslint packages to v5.48.2 (#1278) (69d56a7)

angular-eslint/angular-eslint (@angular-eslint/template-parser)
v16.0.3
Compare Source
Note: Version bump only for package @angular-eslint/template-parser
v16.0.2
Compare Source
Note: Version bump only for package @angular-eslint/template-parser
v16.0.1
Compare Source
Note: Version bump only for package @angular-eslint/template-parser
v16.0.0
Compare Source
Note: Version bump only for package @angular-eslint/template-parser
15.2.1 (2023-02-10)
Note: Version bump only for package @angular-eslint/template-parser

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: public/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/cli
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/cli@">= 16.0.0 < 17.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/@angular-eslint/schematics
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-06-24T11_18_22_638Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-06-24T11_18_22_638Z-debug-0.log

File name: admin/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/cli
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/cli@">= 16.0.0 < 17.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/@angular-eslint/schematics
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-06-24T11_18_31_325Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-06-24T11_18_31_325Z-debug-0.log

Most minor and point updates are blocked by jest-preset-angular, which still has to update.  For now let's close these angular updates and wait.


Enable incremental build on Linux

Would you mind rebasing this on testing/2.0?    Right now the master branch is paused as I get the 2.0 refactoring done, so if this is open against master it'll sit here for a while until I'm reading to merge testing/2.0.  (Same for any other open PRs.)
FYI now that the giant refactoring is done future deltas will be much smaller so I'll be merging PRs quicker.

This PR is based on #335 which was merged into master, so it's easier to keep it target master to avoid possible future conflicts (when merging testing/2.0).

Ah ok, sorry for my confusion.  Re-target master then and I'll merge this one.

Had to roll this one back due to build issues:

  Time Elapsed 00:00:01.08
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Arrays"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Arrays"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Arrays"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Arrays"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/ClrObjects"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/ClrObjects"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/ClrObjects"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/ClrObjects"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/FinalizationQueue"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/FinalizationQueue"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/FinalizationQueue"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/FinalizationQueue"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCHandles"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCHandles"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCHandles"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCHandles"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot2"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot2"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot2"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot2"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/NestedException"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/NestedException"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/NestedException"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/NestedException"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Types"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Types"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Types"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Types"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(153,5): error MSB3680: The source file "Arrays/coredump" does not exist.
##[error]src/TestTargets/TestTargets.proj(153,5): error MSB3680: The source file "Arrays/coredump" does not exist.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Arrays"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Arrays"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Arrays"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Arrays"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/ClrObjects"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/ClrObjects"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/ClrObjects"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/ClrObjects"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/FinalizationQueue"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/FinalizationQueue"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/FinalizationQueue"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/FinalizationQueue"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCHandles"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCHandles"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCHandles"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCHandles"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot2"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot2"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot2"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/GCRoot2"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/NestedException"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/NestedException"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/NestedException"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/NestedException"" exited with code 131.
  A fatal error occurred. The required library libhostfxr.so could not be found.
  If this is a self-contained application, that library should exist in [/__w/1/s/src/TestTargets/bin/x64/].
  If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Types"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Types"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Types"" exited with code 131.
##[error]src/TestTargets/TestTargets.proj(152,5): error MSB3073: The command ""/__w/1/s/src/TestTargets/bin/x64/Types"" exited with code 131.
/__w/1/s/src/TestTargets/TestTargets.proj(153,5): error MSB3680: The source file "Arrays/coredump" does not exist.
##[error]src/TestTargets/TestTargets.proj(153,5): error MSB3680: The source file "Arrays/coredump" does not exist.
  Running tests: /__w/1/s/artifacts/bin/Microsoft.Diagnostics.Runtime.UnitTests/Debug/netcoreapp3.0/Microsoft.Diagnostics.Runtime.UnitTests.dll [netcoreapp3.0|x64]
  Tests succeeded: /__w/1/s/artifacts/bin/Microsoft.Diagnostics.Runtime.UnitTests/Debug/netcoreapp3.0/Microsoft.Diagnostics.Runtime.UnitTests.dll [netcoreapp3.0|x64]
  Successfully created package '/__w/1/s/artifacts/packages/Debug/Shipping/Microsoft.Diagnostics.Runtime.1.1.0-ci.nupkg'.```

I'm still working on getting PR builds turned on for the repo.

Using dotnet CLI to run the executables may resolve the failures. Shall I open a new one?

Sure open a new one.  The overall change itself is fine, it just reacted badly running build.sh.  I'll test the next PR before merging.  =)


list or grid

The addon works 99% perfectly, but no matter I change the subscription view to list, when refreshing or reentering it resets to the grid mode

Well, I deleted YT cookies and that worked. I hope it'll be fine.

is there a doc where the different effects of the pref values are listed/explained? (probs not)
you set f6 to 8 (why?). after that yt changes that to 42008 for me. After switching to list mode it's 42009.
I added the add-on in debugging mode and setting f6 to 42009 keeps it in list mode (mostly). So that's not a good fix >_>


Power connection issues

Howdy,
Discovered today that your cables will connect

IE capacitors
Actually Additions machine (tested with energiser)
AE2 (tested with Energy Acceptor and a growth accelerator)
XU2 coal generator
TechReborn coal generator
NeoTech generator
RFTools Shield Projector

but will not connect:

RFTools powercells (tested with all cable variants)
Woot (mob loot factory mod)

Cheers!

In the above post, I was just testing if they connected. Today I've been testing if they work.
Power source is a TechReborn coal gen.
Power consumers are an ActuallyAdditions Energiser and an IE LV capacitor.
I'm using TheOneProbe to monitor the power levels.
Connecting using a Redstone Fluxed Wire
TOP reports the Energizer's power seems to be bouncing up and down.
The IE capacitor's value is increasing but in the negative direction!
In both cases, when connected with IE's LV wires, the energy flow is as expected.
Cheers!
ImmersiveEngineering 0.10-54
ActuallyAdditions 1.10.2-r97
TechReborn 1.10.2-<IP_ADDRESS>
FluxedRedstone <IP_ADDRESS>

Should be a lot better in the next version.


dotnet publish now fails in ubuntu-latest

dotnet publish now fails when using ubuntu-latest image with error No usable version of the libssl was found. It was working Dec 16th. I'm guessing it has something to do with the upgrade to Ubuntu 20.04. Changing the image from ubuntu-latest to ubuntu-18.04 fixes the issue. Here is the log of the error:
2020-12-18T05:08:43.4371600Z ##[section]Starting: Build backend web artifacts
2020-12-18T05:08:43.4379810Z ==============================================================================
2020-12-18T05:08:43.4380308Z Task         : Command line
2020-12-18T05:08:43.4380642Z Description  : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
2020-12-18T05:08:43.4380968Z Version      : 2.178.0
2020-12-18T05:08:43.4381205Z Author       : Microsoft Corporation
2020-12-18T05:08:43.4381556Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
2020-12-18T05:08:43.4381964Z ==============================================================================
2020-12-18T05:08:43.6341075Z Generating script.
2020-12-18T05:08:43.6342255Z Script contents:
2020-12-18T05:08:43.6343064Z dotnet publish -c Release -o "/home/vsts/work/1/s/.publish/web" /p:Version=<IP_ADDRESS>
2020-12-18T05:08:43.6343564Z ========================== Starting Command Output ===========================
2020-12-18T05:08:43.6350149Z [command]/usr/bin/bash --noprofile --norc /home/vsts/work/_temp/eacf9d3b-ced1-4231-8ff9-6279f1af3571.sh
2020-12-18T05:08:43.7409328Z
2020-12-18T05:08:43.7428442Z Welcome to .NET Core!
2020-12-18T05:08:43.7429380Z ---------------------
2020-12-18T05:08:43.7430008Z Learn more about .NET Core: https://aka.ms/dotnet-docs
2020-12-18T05:08:43.7430727Z Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli-docs
2020-12-18T05:08:43.7431154Z
2020-12-18T05:08:43.7431351Z Telemetry
2020-12-18T05:08:43.7431641Z ---------
2020-12-18T05:08:43.7432922Z The .NET Core tools collect usage data in order to help us improve your experience. The data is anonymous and doesn't include command-line arguments. The data is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.
2020-12-18T05:08:43.7433666Z
2020-12-18T05:08:43.7434204Z Read more about .NET Core CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry
2020-12-18T05:08:43.7434574Z
2020-12-18T05:08:43.7434744Z Configuring...
2020-12-18T05:08:43.7435156Z --------------
2020-12-18T05:08:43.7435672Z A command is running to populate your local package cache to improve restore speed and enable offline access. This command takes up to one minute to complete and only runs once.
2020-12-18T05:08:52.7178287Z Decompressing .......... 8970 ms
2020-12-18T05:09:24.5073479Z Expanding .......... 31636 ms
2020-12-18T05:09:24.5609005Z No usable version of the libssl was found
2020-12-18T05:09:27.1877099Z /home/vsts/work/_temp/eacf9d3b-ced1-4231-8ff9-6279f1af3571.sh: line 1:  1762 Aborted                 (core dumped) dotnet publish -c Release -o "/home/vsts/work/1/s/.publish/web" /p:Version=<IP_ADDRESS>
2020-12-18T05:09:27.1947008Z ##[error]Bash exited with code '134'.
2020-12-18T05:09:27.2122308Z ##[section]Finishing: Build backend web artifacts

Hello, @muhasaho
Could you please check if the installation of libssl1.0.0 resolves the issue?
pkgName=libssl1.0.0_1.0.2n-1ubuntu5.5_amd64.deb
wget "http://us.archive.ubuntu.com/ubuntu/pool/main/o/openssl1.0/${pkgName}"
sudo dpkg -i $pkgName

Feel free to open the thread if you have any concerns.


"Jumping" focus between the JCEF intances

STR with Digma Plugin:

Open the Main Digma panel
Open Observability Digma panel
Switch to another desktop application (IDE and the plugin panels will lose the focus)
Click anywhere in the Observability panels

https://github.com/user-attachments/assets/3d085b84-79aa-4004-b311-f8b9de2e50f0
Current behavior:
Both JCEF panels try to steal focus
Expected behavior:
Only the panel that has been clicked on should have the focus
It seems like this is the Intellij problem, as it also reproduces with the Intellij What's New page.
STR:

Go to Help -> What's New in IntelliJ IDEA
Open it multiple times in different editors side by side
Switch to another desktop application  (IDE and the editors will lose the focus)
Click on one of the editors

https://github.com/user-attachments/assets/590213bf-50c3-4fb2-9966-69d7d0ec4388
Current behavior:
Both editors try to steal the focus
Expected behavior:
Only the tab that has been clicked on should have the focus
IntelliJ IDEA 2024.2.1 (Community Edition)
Build #IC-242.21829.142, built on August 28, 2024
Runtime version: 21.0.3+13-b509.11 aarch64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.lwawt.macosx.LWCToolkit
macOS 14.6.1
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 2048M
Cores: 12
Metal Rendering is ON
Registry:
  ide.experimental.ui=true
  i18n.locale=
Non-Bundled Plugins:
  org.jetbrains.plugins.gitlab (242.21829.162)
  org.digma.intellij (2.0.383+242)
Kotlin: 242.21829.142-IJ

Also reproduces on Linux

Corresponding issue in Jetbrains Youtrack: https://youtrack.jetbrains.com/issue/IJPL-161147/Focus-is-endlessly-flickering-between-Webviews-in-split-view


How to generate the intermediate file {}-gc.json

I found that the {}-gc.json file was missing in the experiment of the reproduction model on the RE-DOCRED dataset, I would like to ask you how to generate this intermediate file?

Hi, the {}-gc.json is generated by src/prepro.py, as mentioned in Step 2.


Frame window timed out error from signInSilent(User Manager)

Hi Team,
I am accessing oidc-client from User manager signInSilent method. I am getting the following error in response. "Frame window timed out". Version of oidc-client is 1.5.1-beta.1
Though I am passing the following parameters as required.
_silent_redirect_uri: “http://localhost:3010/silent.html”
_silentRequestTimeout: 10000
_automaticSilentRenew: true
_validateSubOnSilentRenew: false
_includeIdTokenInSilentRenew: true
_query_status_response_type: “id_token”
Please help me with this as I am stuck since long.

It means the window has timed out -- probably due to a UI being shown (like an error page). No one will see that, so the iframe has a timeout on it. Find out why the request causes the error page to be shown.

I tried to separate the silent js code from index.js code and loaded 2 separate files.
The issue is not there now. Is it because I was loading one big JS file in the silent .html?

Hi swetapatnaik,
I have the same  "Frame window timed out" error.
It's very hard to troubleshoot.
I have no errors in IdentityServer logs (server side). On the client side, on Chrome Network tab, I just have some "<MY_IDENTITY_SERVER>/.well-known/openid-configuration" GET requests in "cancelled" state (marked as error in Chrome).
But I cannot figure out why.
PS
You are using an old version of the JS library

@brockallen We are getting the same issues, Is there any known work around?

@brockallen We are getting the same issues, Is there any known work around?

Not sure. Time outs are commonly because an error being displayed in the iframe, so check your STS logs.

Not sure. Time outs are commonly because an error being displayed in the iframe, so check your STS logs.

We are not using an iFrame, its a completely different route - exactly as in this example
https://github.com/maxmantz/redux-oidc-example
the only difference is the index.js (typescript app)
import { WebStorageStateStore } from 'oidc-client';
import { OIDC_PREFIX } from '../src/store/types';
import CookieWebStorageStore from '../src/auth/CookieWebStorageStore';
import { createUserManager } from 'redux-oidc';

const userStore = new WebStorageStateStore({
  prefix: OIDC_PREFIX,
  store: new CookieWebStorageStore(false)
});

const UserManager = createUserManager({ userStore });

UserManager.signinSilentCallback()
  .then(() => {
    console.log('signinSilentCallback Fired');
  })
  .catch(err => {
    console.log(err);
  });

We are not using an iFrame, its a completely different route - exactly as in this example
https://github.com/maxmantz/redux-oidc-example
the only difference is the index.js (typescript app)
import { WebStorageStateStore } from 'oidc-client';
import { OIDC_PREFIX } from '../src/store/types';
import CookieWebStorageStore from '../src/auth/CookieWebStorageStore';
import { createUserManager } from 'redux-oidc';

const userStore = new WebStorageStateStore({
  prefix: OIDC_PREFIX,
  store: new CookieWebStorageStore(false)
});

const UserManager = createUserManager({ userStore });

UserManager.signinSilentCallback()
  .then(() => {
    console.log('signinSilentCallback Fired');
  })
  .catch(err => {
    console.log(err);
  });

No, check your STS logs -- the token server's logs.

No, check your STS logs -- the token server's logs.

Not sure. Time outs are commonly because an error being displayed in the iframe, so check your STS logs.

I also have the same problem. I cannot figure out why the iframe is timing out. Fiddler & IdentityServer4 log don't report any problems. Also Chrome & Firefox network tabs aren't showing any problems.
After the first expiration the new token was retrieved and a few seconds after that, the timeout occurs:
oidc-client.min.js:1 Event: Raising event: Access token expiring
...
UserManager._signinStart: got signin request
oidc-client.min.js:1 IFrameWindow.navigate: Using timeout of: 10000
...
VM39 0.chunk.js:89715 UserManager.signinRedirectCallback: successful, signed in sub:  34CF65ED-B85B-4812-9175-C79FBF267CE6
...
User.fromStorageString
VM39 0.chunk.js:89715 UserManager.getUser: user loaded
VM39 0.chunk.js:89709 UserManagerEvents.load
VM39 0.chunk.js:89709 AccessTokenEvents.load: access token present, remaining duration: 119
VM39 0.chunk.js:89709 AccessTokenEvents.load: registering expiring timer in: 59
VM39 0.chunk.js:89709 Timer.init timer Access token expiring skipping initialization since already initialized for expiration:<PHONE_NUMBER>
VM39 0.chunk.js:89709 AccessTokenEvents.load: registering expired timer in: 120
VM39 0.chunk.js:89709 Timer.init timer Access token expired skipping initialization since already initialized for expiration:<PHONE_NUMBER>
oidc-client.min.js:1 CheckSessionIFrame: unchanged message from check session op iframe
oidc-client.min.js:1 IFrameWindow.message
VM39 0.chunk.js:89709 CheckSessionIFrame: unchanged message from check session op iframe
oidc-client.min.js:1 Timer.callback; Access token expired timer expires in: 51
oidc-client.min.js:1 IFrameWindow.timeout
oidc-client.min.js:1 IFrameWindow: cleanup
index.js:1 Frame window timed out
oidc-client.min.js:1 UserManagerEvents._raiseSilentRenewError Frame window timed out

Even if I set the timeout higher, the timeout error will still be present even though it was successful (according to the logs)

I had this issue, silent sign-in was making the request successfully to the server but the iframe would error.
This was occurring on my local machine, in development. The app was being served over localhost with a self-signed certificate.
The solution seemed to be to use a local Certificate Authority by using the 'mkcert' util, rather than a self-signed certificate .
It worked after that.


uart_control does not work on Raspi 4

uart_control does not work on Raspi 4

Thanks to @astuder this is now fixed.


Expose permissiveParsing as an AppSetting

User story
As an admin, I want to have the ability to turn PermissiveParsing on or off so that I can have control over how strict the data validation is on my server
Acceptance criteria

PermissiveParsing is a setting in AppSettings
Setting is applied to all FHIR Json/Xml Parsers

Settings are currently set in a static: Microsoft.Health.Fhir.Core.Features.DefaultParserSettings

Strictness may affect issues such as #775


Get messaged matches is not working

Get messaged matches is not working. I think TInder updates messes up this script.

Hi @bashback ,
Tinder changed their html layout so I'd need to update all xpaths in order for the project to work again.
Unfortunately, I haven't yet had the time to fix it.
I'll be able to fix it somewhere next week though.

Hi @bashback,
It should work now, I did some quick hot fixes and I'm looking for a cleaner solution future wise.
Anyways, if something wouldn't work as expected, feel free to open a new issue.
Have a nice day!
Fred :)


Menu management

Added Model for Menu Item, Integrated templates for menu list, add, edit.
Done Menu Management CRUD Operations, status change, swap functionality.

Coverage decreased (-3.8%) to 84.875% when pulling dca1711b25f8df6ff5e3b4b0a26f73ecf8c3fa65 on swethanaretla:menu_management into 121df10156f285cc902aa23ff3cd6fd29a858af7 on MicroPyramid:master.


Fix chrome 53 "will-change" side-effect on tooltip

Removing the "will-change" property will cause tooltip disappear immediately after mouseover, but keeping it will make text become blurry.
This solution is from here: http://greensock.com/will-change

This is a known issue, it is fixed in Chrome 54 which is the current stable. Only ChromeOS is behind on 53 currently and it should be getting updated soon.
Thanks for the PR, but since the issue is fixed within the engine already there is no need to remove the property.


JournalToggle has no effect

The journalToggle command, or the <C-j><C-x> shortcut, has no effect when I call it on a checkbox item or a TODO item.
By the way, will this plugin support customizing TODO keywords, like org-mode?
Thank you for writing this helpful plugin!

can i get the buffer or something to generate the bug?

support customizing TODO keywords

it sounds good!

can i get the buffer or something to generate the bug?

I try this feature again. But this time the issue does not occur. Perhaps I made something wrong last time. Sorry!
But I find another issue: when this plugin is enabled and I edit a markdown file, vim lags as I type in  key; when this plugin is disabled, the lagging disappears. I think something in this plugin maybe causes this lagging. Or this plugin interfers with some other plugins that I have installed.

can i get the buffer or something to generate the bug?

I try this feature again. But this time the issue does not occur. Perhaps I made something wrong last time. Sorry!
But I find another issue: when this plugin is enabled and I edit a markdown file, vim lags as I type in Space key; when this plugin is disabled, the lagging disappears. I think something in this plugin maybe causes this lagging. Or this plugin interfers with some other plugins that I have installed.

Update:
I have found out what causes that issue. I change the key mapping to make use of leader key, and this plugin does this: au FileType markdown execute "inoremap " . g:journal_toggle . " <esc>:JournalToggle<cr>a". The two things make my vim recoginize space key as the leader key in insert mode.
I comment out that inoremap line, and everything is OK.


Check lighthouse performance

[ ]  Check the performance of your page

[ ]  Check the SEO optimalization

[ ]  Check the accessibility

[ ]  Check the websites best practices

[ ] Make sure your JS is bugfree and runs smoothly


[RUNTIME] C++ RPC Server

So far most of the logic of RPC session handling is in C++. However, we use frontend languages(python,java) to do the basic incoming request handling.
This issue explores if we can move even more logic to C++, to make it possible to create a bare-metal c++ version of RPC, or reuse more logics across language bindings
General Logic of RPC Server
The current RPC is based on TCP socket. The simplest RPC server can do the following loop

Listen on a port
Accept incoming connection
Trap into RPCServerLoop

Fault tolerant version of RPC Server
Because RPC server can be used for tuning, we need to support timeout and possible fault tolerance when running bad programs, there are two ways to support fault tolerance so far

Fork-based server(used in python)

Master process listens on port and accepts incoming connection
Master process fork a child worker process
Child worker inherits the socket,  trap into RPCServerLoop
Because child worker is isolated from master process, master process can kill the child if there is timeout, and can detect if the child crashes

Watchdog based server (used in android)

Worker process: main thread listens on port and accept incoming connections
Worker process: main thread wake up another watchdog thread
Worker process: The watchdog will sleep until timeout and call exit(0) to quit the current process if there is time-out
Monitor process: the only job of the monitor process is to restart worker process.

Watchdog based server is useful for cases when there is no fork function supported by the system.
Tracker compatible version of RPC Server
In order to be able to run automated optimization with a pool of devices, we want to support reporting to the tracker. Here is a general step

RPC server choose a random magic number
RPC server reports the current resource to the tracker
RPC server listens on the port(normal RPC process)

This way the tracker is aware of the resource and can be used to coordinate things when necessary.
Possible Actionable Items
To make things more portable, I would recommend we implement the following logic in c++

[ ] Tracker reporting logic
[ ] Watchdog based fault tolerance logic

Just like the current RPC server, we do not have to build a complete CLI version, instead, we can expose PackedFuncs that makes things easier to do in the CLI, proposals and contribution of code are welcomed.
Please reply if you are interested in working on this.

cc @yzhliu @eqy @FrozenGene

why don't merge this PR? The C++ RPC is very useful in many embeded device.

#4281


why i the icon missing?

Dear Bootstrap, why the icon is missing? Am i need to put font-awesome in my project?

Result:

for how-to questions, please use stackoverflow or similar. see https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#using-the-issue-tracker


Link to the text "Register and install binding extensions" is not correct in "Changes in triggers and bindings" heading.

I think it should re-direct to"https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-register" instead of "https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-expressions-patterns"

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1df5e2bd-489d-19b2-87d3-d993ebb82021
Version Independent ID: 9e9d9ded-8f40-22be-4654-48c87f2c59e8
Content: Azure Functions runtime versions overview
Content Source: articles/azure-functions/functions-versions.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@vinothrao Thank you for providing your feedback. We will review this and provide an update as appropriate.

@vinothrao The referenced PR will update the correct link to the text "Register and install binding extensions" in the document. Thank you for providing your valuable feedback.

@vinothrao We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


[feature request] Support Edgex Jakarta

What would you like to be added:
Support Edgex Jakarta version, and is not backward compatible with Hanoi.
Why is this needed:
Jakarta is first LTS release.
others
/kind feature

@huiwq1990 The OpenYurt community and the EdgeX community are working closely together to support this feature and it is expected to be released in OpenYurt v0.7.0.

@huiwq1990 The OpenYurt community and the EdgeX community are working closely together to support this feature and it is expected to be released in OpenYurt v0.7.0.

When will OpenYurt v0.7.0 release?

This feature is supported, the code is merged to release-0.2.0


Readme updates - fix images

Change-type: patch
Signed-off-by: Chris Crocker-White<EMAIL_ADDRESS>Hey there, appreciated contributor!
Have you taken a look at the contribution guidelines for this project? To enable our CI to work correctly and version the releases of the project, you need to ensure your commit messages contain the required information detailed here. Thank you!

@balena-ci I self-certify!


Refactor class and enum declaration

class and enum declaration have many common code, which we should extract for better maintainability.

Fixed by https://github.com/jespersm/groovy/commit/f7798a1d6e7ee8bfed67944e4d6c420ea2a26726


Update Giant Swarm website URL

The link shown currently results in a redirect. I'd prefer to have the actual URL in the docs. Thanks!

/lgtm
/approve


Does this paper use the Information Of CAD models?

Well, I found that when we try to generate xyz_crop.pkl  It seems That we only use the depth map of a image,  Can we say that this is a net  Without the help of CAD model?
Or you use CAD model. But I didn't find it.
Thank you.

The depth map for generating xyz should be the rendered depth from CAD models, because the real depth maps are noisy. So yes, we use the CAD information.

The depth map for generating xyz should be the rendered depth from CAD models, because the real depth maps are noisy. So yes, we use the CAD information.

Thank you.but in #24  it doesn't use the CAD Information.

It does. See https://github.com/THU-DA-6D-Pose-Group/GDR-Net/blob/main/tools/lm/lm_pbr_1_gen_xyz_crop.py#L139


Option for specifying the stack growth direction of an architecture

It'd be nice to be able to specify what direction the stack grows for an architecture. Right now binja assumes the stack always grows down, so LLIL_PUSH will subtract from the stack register and LLIL_POP will add to it.
I'm currently trying to make an architecture plugin for yan85 (custom architecture used in CTF challenges on pwn.college). The stack in this architecture grows upwards, but I can't seem to figure out a way to nicely implement this behavior. I've tried to manually implement the push and pop instead of using the normal LLIL_PUSH and LLIL_POP by modifying the stack pointer properly and loading/storing, but it led to an objectively worse looking decompilation.
I imagine the feature wouldn't be too hard to implement, as it would just change whether push and pop either adds or subtracts to the stack, but that's just my guess so I could be completely wrong.

This is also a problem on the 8051 architecture. Another difference is that it pre-increments the SP on push instead of post-incrementing (which can mostly be worked around by subtracting 1 on loads of SP and adding 1 on stores).


fix 780

This PR fixes a divide-by-zero error described in issue 780. https://github.com/ManimCommunity/manim/issues/780
The problem is the default value of faded_line_ratio being set to 0 instead of 1.
Closes #780

This is nice but I think we should add a verification wether faded_line_ratio is equal to zero, and act consequently.
The bug is happening right there :
https://github.com/huguesdevimeux/manim/blob/c83b5ba4b3b4522474eea807f6b1c10298284765/manim/mobject/coordinate_systems.py#L358-L359
        step = (1 / dense_freq) * freq # issue when dense_freq is zero

Why not adding a check and if it is zero, there is faded_line drawn? It would make sense.

@huguesdevimeux can you assist? I'll give you access to push to this branch.

What does a faded_line_ratio of 0 actually mean?

What does a faded_line_ratio of 0 actually mean?

Maybe to not have faded line at all (just a grid)? (it's just a suggestion).

@huguesdevimeux can you assist? I'll give you access to push to this branch.

Sorry, but I don't think I'll be able to commit anything. The best I can do is help you if you need some.

What does a faded_line_ratio of 0 actually mean?

This controls how to divide inbetween lines: 0 doesn't make sense.
Here is the top faded_line_raio = 1, bottom faded_line_raio = 3 output.

If someone sets ratio_faded_lines = 0 we can assume they didn't want any faded lines. In that case we just secretly set it to 1 - i.e. the space between faded lines and the space between non-faded lines is the same... in other words there are no visible faded lines.

Thank you @yamauchih for reporting and @cobordism for implementing.


question about pipelining codeceptjs tests

question: in a dev pipeline, would you start the codeceptjs regression tests within a Grunt-test or with a Jenkins task?
I am not sure where to put it ;)

Why Not just start Them with an npm script (npm test for Instance) and run them with a shell task?

because I want it to start automatically when there happens a commit to a specific branch.

Looks like you have to start tests after your application was deployed. What CI system do you use? Like @hubidu I recommend to use npm task - it's the easiest way to run tests

or with a Jenkins task?

My choice is to use Jenkins task. Split test by groups (configured by --grep) and run such tasks in parallel


asyncio bulkCmd does a get-next instead of get-bulk

Perhaps a reproducer would be helpful for analysis.

to whom it may concern ...
problem lies in this line:
CommunityData('public', mpModel=0),

mpModel=0 means SNMPv1 while mpModel=1 means SNMPv2c
getbulk was introduced in v2c so when using v1 the bulk request is silently replaced by  a next request

Right! That's what should happen according to RFC2576.


iflipb-current-buffer-face appears in Ibuffer

Steps to reproduce:

Call iflip-next-buffer to make some buffer the current iflipb buffer
M-x ibuffer

After doing so, the name of the current iflipb buffer will be shown using iflipb-current-buffer-face inside Ibuffer. I've been able to reproduce this on Emacs 28.1, with iflip as the only external package installed.

Thanks for the bug report! Will fix.


[BUG]  entailment_xnli_bert_azureml import error with AmlCompute and also the maximum number of nodes in the cluster should be 4

Description

How do we replicate the bug?

Expected behavior (i.e. solution)

Other Comments

changes are in https://github.com/microsoft/nlp-recipes/pull/499


[admin] merge to live

Docs Build status updates of commit e9a4fec:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/Access.AcBrowseToObjectType.md
:white_check_mark:Succeeded
View

api/Access.Form.DatasheetFontName.md
:white_check_mark:Succeeded
View

api/PowerPoint.shapes.addinkshapefromxml.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Unwrapping a promise in Event Loop Integration

How can I unwrap a promise when integrated with Event Loop?

If you're using an event loop, then you don't need to unwrap or wait on a promise. Instead, you should use promise callbacks to receive the result of a promise.
The only way to unwrap a promise is to call wait on it. This could have consequences in an event loop based application in that waiting could cause a promise fulfilled with a promise to block on that  promise to complete before returning a value.


New version

@JackDanger can we bump version. Or better yet, can you email me the pypi details so i can automate it :wink:

I've now released Moto version 1.1.25
@terrycain what's your PyPi username? I'll see if I can add you to the project!

@spulec Can you add @terrycain to the PyPi project so Terry can do releases?
It's probably time we add a more formalized release process. I'll write a short guide for contributors and add some helpful scripts.

I've created some new guides for maintainers to easily release new versions of Moto. It's now a 3-command process: #1355

can we get another new release?  Would like one with https://github.com/spulec/moto/pull/2055 to avoid having to install this via git

Moto is on continuous release now. We cut a pre-release for each commit to master.