Waiting for '/controller_manager' node to existIssue name

Affected ROS2 Driver version(s)
2.2.8-1jammy.20230920.011431
Used ROS distribution.
Humble
Which combination of platform is the ROS driver running on.
Ubuntu Linux with standard kernel
How is the UR ROS2 Driver installed.
From binary packets
Which robot platform is the driver connected to.
UR E-series robot
Robot SW / URSim version(s)
N/A
How is the ROS driver used.
Others
Issue details
Summary
I am trying to use UR5e robot in simulation with MoveIt package. However, I am getting the following error upon invoking ur_robot_driver: Waiting for '/controller_manager' node to exist
Issue details
ravi@dell:~/moveit_ws_humble$ ros2 launch ur_robot_driver ur5e.launch.py robot_ip:=aaa.bbb.ccc.ddd use_fake_hardware:=true initial_joint_controller:=joint_trajectory_controller launch_rviz:=false
[INFO] [launch]: All log files can be found below /home/ravi/.ros/log/2023-09-26-21-04-28-563130-dell-54645
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [ros2_control_node-1]: process started with pid [54648]
[INFO] [robot_state_publisher-2]: process started with pid [54650]
[INFO] [spawner-3]: process started with pid [54652]
[INFO] [spawner-4]: process started with pid [54654]
[INFO] [spawner-5]: process started with pid [54656]
[INFO] [spawner-6]: process started with pid [54658]
[INFO] [spawner-7]: process started with pid [54660]
[INFO] [spawner-8]: process started with pid [54662]
[robot_state_publisher-2] [INFO] [1695729868.881985946] [robot_state_publisher]: got segment base
[robot_state_publisher-2] [INFO] [1695729868.882022555] [robot_state_publisher]: got segment base_link
[robot_state_publisher-2] [INFO] [1695729868.882026571] [robot_state_publisher]: got segment base_link_inertia
[robot_state_publisher-2] [INFO] [1695729868.882029125] [robot_state_publisher]: got segment flange
[robot_state_publisher-2] [INFO] [1695729868.882031542] [robot_state_publisher]: got segment forearm_link
[robot_state_publisher-2] [INFO] [1695729868.882033776] [robot_state_publisher]: got segment ft_frame
[robot_state_publisher-2] [INFO] [1695729868.882035965] [robot_state_publisher]: got segment shoulder_link
[robot_state_publisher-2] [INFO] [1695729868.882038181] [robot_state_publisher]: got segment tool0
[robot_state_publisher-2] [INFO] [1695729868.882040484] [robot_state_publisher]: got segment upper_arm_link
[robot_state_publisher-2] [INFO] [1695729868.882042781] [robot_state_publisher]: got segment world
[robot_state_publisher-2] [INFO] [1695729868.882044921] [robot_state_publisher]: got segment wrist_1_link
[robot_state_publisher-2] [INFO] [1695729868.882047119] [robot_state_publisher]: got segment wrist_2_link
[robot_state_publisher-2] [INFO] [1695729868.882049292] [robot_state_publisher]: got segment wrist_3_link
[ros2_control_node-1] [INFO] [1695729868.886599962] [resource_manager]: Loading hardware 'ur5e'
[ros2_control_node-1] [INFO] [1695729868.886845052] [resource_manager]: Initialize hardware 'ur5e'
[ros2_control_node-1] [WARN] [1695729868.886858260] [mock_generic_system]: Parameter 'fake_sensor_commands' has been deprecated from usage. Use'mock_sensor_commands' instead.
[ros2_control_node-1] [WARN] [1695729868.886865384] [mock_generic_system]: Parsing of optional initial interface values failed or uses a deprecated format. Add initial values for every state interface in the ros2_control.xacro. For example:
[ros2_control_node-1] <state_interface name="velocity">
[ros2_control_node-1]   <param name="initial_value">0.0</param>
[ros2_control_node-1] </state_interface>
[ros2_control_node-1] [INFO] [1695729868.886891692] [resource_manager]: Successful initialization of hardware 'ur5e'
[ros2_control_node-1] [INFO] [1695729868.886961153] [resource_manager]: 'configure' hardware 'ur5e'
[ros2_control_node-1] [INFO] [1695729868.886963879] [resource_manager]: Successful 'configure' of hardware 'ur5e'
[ros2_control_node-1] [INFO] [1695729868.886976560] [resource_manager]: 'activate' hardware 'ur5e'
[ros2_control_node-1] [INFO] [1695729868.886978786] [resource_manager]: Successful 'activate' of hardware 'ur5e'
[ros2_control_node-1] [INFO] [1695729868.887706763] [controller_manager]: update rate is 500 Hz
[ros2_control_node-1] [INFO] [1695729868.887833335] [controller_manager]: RT kernel is recommended for better performance
[spawner-7] [INFO] [1695729871.101916718] [spawner_force_torque_sensor_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-3] [INFO] [1695729871.102032243] [spawner_joint_trajectory_controller]: Waiting for '/controller_manager' node to exist
[spawner-5] [INFO] [1695729871.105224853] [spawner_io_and_status_controller]: Waiting for '/controller_manager' node to exist
[spawner-6] [INFO] [1695729871.118154070] [spawner_speed_scaling_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-4] [INFO] [1695729871.120449365] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-8] [INFO] [1695729871.126219358] [spawner_forward_position_controller]: Waiting for '/controller_manager' node to exist
[spawner-7] [INFO] [1695729873.113261603] [spawner_force_torque_sensor_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-3] [INFO] [1695729873.114233200] [spawner_joint_trajectory_controller]: Waiting for '/controller_manager' node to exist
[spawner-5] [INFO] [1695729873.122779362] [spawner_io_and_status_controller]: Waiting for '/controller_manager' node to exist
[spawner-6] [INFO] [1695729873.130581032] [spawner_speed_scaling_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-4] [INFO] [1695729873.132446282] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-8] [INFO] [1695729873.137217201] [spawner_forward_position_controller]: Waiting for '/controller_manager' node to exist
[spawner-7] [INFO] [1695729875.126422869] [spawner_force_torque_sensor_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-3] [INFO] [1695729875.126821062] [spawner_joint_trajectory_controller]: Waiting for '/controller_manager' node to exist
[spawner-5] [INFO] [1695729875.134703770] [spawner_io_and_status_controller]: Waiting for '/controller_manager' node to exist
[spawner-6] [INFO] [1695729875.142291238] [spawner_speed_scaling_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-4] [INFO] [1695729875.143345806] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-8] [INFO] [1695729875.149365702] [spawner_forward_position_controller]: Waiting for '/controller_manager' node to exist
[spawner-3] [INFO] [1695729877.138539819] [spawner_joint_trajectory_controller]: Waiting for '/controller_manager' node to exist
[spawner-7] [INFO] [1695729877.138570453] [spawner_force_torque_sensor_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-5] [INFO] [1695729877.147110484] [spawner_io_and_status_controller]: Waiting for '/controller_manager' node to exist
[spawner-6] [INFO] [1695729877.154552363] [spawner_speed_scaling_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-4] [INFO] [1695729877.155756134] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-8] [INFO] [1695729877.161136004] [spawner_forward_position_controller]: Waiting for '/controller_manager' node to exist
[spawner-3] [ERROR] [1695729879.150882900] [spawner_joint_trajectory_controller]: Controller manager not available
[spawner-7] [ERROR] [1695729879.151388413] [spawner_force_torque_sensor_broadcaster]: Controller manager not available
[spawner-5] [ERROR] [1695729879.159142295] [spawner_io_and_status_controller]: Controller manager not available
[spawner-6] [ERROR] [1695729879.167091908] [spawner_speed_scaling_state_broadcaster]: Controller manager not available
[spawner-4] [ERROR] [1695729879.169221686] [spawner_joint_state_broadcaster]: Controller manager not available
[spawner-8] [ERROR] [1695729879.172614731] [spawner_forward_position_controller]: Controller manager not available
^C[WARNING] [launch]: user interrupted with ctrl-c (SIGINT)
[ros2_control_node-1] [INFO] [1695729885.930441175] [rclcpp]: signal_handler(signum=2)
[robot_state_publisher-2] [INFO] [1695729885.930568431] [rclcpp]: signal_handler(signum=2)
^C[WARNING] [launch]: user interrupted with ctrl-c (SIGINT) again, ignoring...
[robot_state_publisher-2] [INFO] [1695729886.522478273] [rclcpp]: signal_handler(signum=2)
[ERROR] [ros2_control_node-1]: process has died [pid 54648, exit code -2, cmd '/opt/ros/humble/lib/controller_manager/ros2_control_node --ros-args --params-file /tmp/launch_params_3kkmvc2p --params-file /opt/ros/humble/share/ur_robot_driver/config/ur5e_update_rate.yaml --params-file /opt/ros/humble/share/ur_robot_driver/config/ur_controllers.yaml'].
[ERROR] [spawner-8]: process[spawner-8] failed to terminate '5' seconds after receiving 'SIGINT', escalating to 'SIGTERM'
[ERROR] [spawner-7]: process[spawner-7] failed to terminate '5' seconds after receiving 'SIGINT', escalating to 'SIGTERM'
[ERROR] [spawner-6]: process[spawner-6] failed to terminate '5' seconds after receiving 'SIGINT', escalating to 'SIGTERM'
[ERROR] [spawner-5]: process[spawner-5] failed to terminate '5' seconds after receiving 'SIGINT', escalating to 'SIGTERM'
[ERROR] [spawner-4]: process[spawner-4] failed to terminate '5' seconds after receiving 'SIGINT', escalating to 'SIGTERM'
[ERROR] [spawner-3]: process[spawner-3] failed to terminate '5' seconds after receiving 'SIGINT', escalating to 'SIGTERM'
[ERROR] [robot_state_publisher-2]: process[robot_state_publisher-2] failed to terminate '5' seconds after receiving 'SIGINT', escalating to 'SIGTERM'
[INFO] [spawner-8]: sending signal 'SIGTERM' to process[spawner-8]
[INFO] [spawner-7]: sending signal 'SIGTERM' to process[spawner-7]
[INFO] [spawner-6]: sending signal 'SIGTERM' to process[spawner-6]
[INFO] [spawner-5]: sending signal 'SIGTERM' to process[spawner-5]
[INFO] [spawner-4]: sending signal 'SIGTERM' to process[spawner-4]
[INFO] [spawner-3]: sending signal 'SIGTERM' to process[spawner-3]
[INFO] [robot_state_publisher-2]: sending signal 'SIGTERM' to process[robot_state_publisher-2]
[ERROR] [spawner-8]: process has died [pid 54662, exit code -15, cmd '/opt/ros/humble/lib/controller_manager/spawner forward_position_controller --controller-manager /controller_manager --controller-manager-timeout 10 --inactive --ros-args'].
[ERROR] [spawner-7]: process has died [pid 54660, exit code -15, cmd '/opt/ros/humble/lib/controller_manager/spawner force_torque_sensor_broadcaster --controller-manager /controller_manager --controller-manager-timeout 10 --ros-args'].
[ERROR] [spawner-6]: process has died [pid 54658, exit code -15, cmd '/opt/ros/humble/lib/controller_manager/spawner speed_scaling_state_broadcaster --controller-manager /controller_manager --controller-manager-timeout 10 --ros-args'].
[ERROR] [spawner-5]: process has died [pid 54656, exit code -15, cmd '/opt/ros/humble/lib/controller_manager/spawner io_and_status_controller --controller-manager /controller_manager --controller-manager-timeout 10 --ros-args'].
[ERROR] [spawner-4]: process has died [pid 54654, exit code -15, cmd '/opt/ros/humble/lib/controller_manager/spawner joint_state_broadcaster --controller-manager /controller_manager --controller-manager-timeout 10 --ros-args'].
[robot_state_publisher-2] [INFO] [1695729890.955293713] [rclcpp]: signal_handler(signum=15)
[ERROR] [spawner-3]: process has died [pid 54652, exit code -15, cmd '/opt/ros/humble/lib/controller_manager/spawner joint_trajectory_controller -c /controller_manager --controller-manager-timeout 10 --ros-args'].
[ERROR] [robot_state_publisher-2]: process[robot_state_publisher-2] failed to terminate '10.0' seconds after receiving 'SIGTERM', escalating to 'SIGKILL'
[INFO] [robot_state_publisher-2]: sending signal 'SIGKILL' to process[robot_state_publisher-2]
[ERROR] [robot_state_publisher-2]: process has died [pid 54650, exit code -9, cmd '/opt/ros/humble/lib/robot_state_publisher/robot_state_publisher --ros-args --params-file /tmp/launch_params___muhxef'].

Additional Info
During this error I noticed that ros2 control list_controllers does not return anything and stays alive forever.
Relevant log output
No response
Accept Public visibility

[X] I agree to make this context public

We'll have to check that. Looking at your log output I cannot immediately spot something wrong.

Did you manage to solve this? I am experiencing a very similar issue after having updated my laptop to a configuration very similar to yours.

Hey, Running into the same issue. Does anyone know how to fix this problem?
ros2 launch ur_robot_driver ur_control.launch.py ur_type:=ur3 robot_ip:=yyy.yyy.yyy.yyy use_fake_hardware:=true initial_joint_controller:=joint_trajectory_controller launch_rviz:=false
[INFO] [launch]: All log files can be found below /home/rtc2/.ros/log/2024-02-02-15-40-24-824311-rtc2-715303
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [ros2_control_node-1]: process started with pid [715306]
[INFO] [urscript_interface-2]: process started with pid [715308]
[INFO] [robot_state_publisher-3]: process started with pid [715310]
[INFO] [spawner-4]: process started with pid [715312]
[INFO] [spawner-5]: process started with pid [715314]
[INFO] [spawner-6]: process started with pid [715316]
[INFO] [spawner-7]: process started with pid [715318]
[INFO] [spawner-8]: process started with pid [715320]
[INFO] [spawner-9]: process started with pid [715333]
[ros2_control_node-1] text not specified in the tf_prefix tag
[ros2_control_node-1] [INFO] [1706906425.535028220] [resource_manager]: Loading hardware 'ur3'
[ros2_control_node-1] [INFO] [1706906425.537200950] [resource_manager]: Initialize hardware 'ur3'
[ros2_control_node-1] [INFO] [1706906425.537726822] [resource_manager]: Successful initialization of hardware 'ur3'
[ros2_control_node-1] [INFO] [1706906425.538160434] [resource_manager]: 'configure' hardware 'ur3'
[ros2_control_node-1] [INFO] [1706906425.538465117] [resource_manager]: Successful 'configure' of hardware 'ur3'
[ros2_control_node-1] [INFO] [1706906425.538744264] [resource_manager]: 'activate' hardware 'ur3'
[ros2_control_node-1] [INFO] [1706906425.539007880] [URPositionHardwareInterface]: Starting ...please wait...
[ros2_control_node-1] [INFO] [1706906425.539265621] [URPositionHardwareInterface]: Initializing driver...
[robot_state_publisher-3] [INFO] [1706906425.541136097] [robot_state_publisher]: got segment base
[robot_state_publisher-3] [INFO] [1706906425.541264056] [robot_state_publisher]: got segment base_link
[robot_state_publisher-3] [INFO] [1706906425.541275136] [robot_state_publisher]: got segment base_link_inertia
[robot_state_publisher-3] [INFO] [1706906425.541279244] [robot_state_publisher]: got segment flange
[robot_state_publisher-3] [INFO] [1706906425.541282796] [robot_state_publisher]: got segment forearm_link
[robot_state_publisher-3] [INFO] [1706906425.541286038] [robot_state_publisher]: got segment ft_frame
[robot_state_publisher-3] [INFO] [1706906425.541289443] [robot_state_publisher]: got segment shoulder_link
[robot_state_publisher-3] [INFO] [1706906425.541292687] [robot_state_publisher]: got segment tool0
[robot_state_publisher-3] [INFO] [1706906425.541295862] [robot_state_publisher]: got segment upper_arm_link
[robot_state_publisher-3] [INFO] [1706906425.541299084] [robot_state_publisher]: got segment world
[robot_state_publisher-3] [INFO] [1706906425.541302353] [robot_state_publisher]: got segment wrist_1_link
[robot_state_publisher-3] [INFO] [1706906425.541305544] [robot_state_publisher]: got segment wrist_2_link
[robot_state_publisher-3] [INFO] [1706906425.541308652] [robot_state_publisher]: got segment wrist_3_link
[ros2_control_node-1] [ERROR] [1706906425.554576341] [UR_Client_Library:]: Failed to get address for yyy.yyy.yyy.yyy:30002
[ros2_control_node-1] [ERROR] [1706906425.564421706] [UR_Client_Library:]: Failed to get address for yyy.yyy.yyy.yyy:30004
[ros2_control_node-1] [ERROR] [1706906425.564926189] [UR_Client_Library:]: Attempt to write on a non-connected socket
[ros2_control_node-1] [ERROR] [1706906425.565219455] [UR_Client_Library:]: Sending RTDE pause command failed!
[ros2_control_node-1] [FATAL] [1706906425.565489885] [URPositionHardwareInterface]: Failed to connect to robot. Please check if the robot is booted and connected.
[ros2_control_node-1] [INFO] [1706906425.565749437] [resource_manager]: Failed to 'activate' hardware 'ur3'
[ros2_control_node-1] [INFO] [1706906425.578735163] [controller_manager]: update rate is 125 Hz
[ros2_control_node-1] [INFO] [1706906425.582436167] [controller_manager]: RT kernel is recommended for better performance
[ros2_control_node-1] [INFO] [1706906426.221011929] [controller_manager]: Loading controller 'joint_trajectory_controller'
[ros2_control_node-1] [WARN] [1706906426.231276927] [joint_trajectory_controller]: [Deprecated]: "allow_nonzero_velocity_at_trajectory_end" is set to true. The default behavior will change to false.
[spawner-4] [INFO] [1706906426.250350965] [spawner_joint_trajectory_controller]: Loaded joint_trajectory_controller
[ros2_control_node-1] [INFO] [1706906426.251610351] [controller_manager]: Configuring controller 'joint_trajectory_controller'
[ros2_control_node-1] [INFO] [1706906426.251757213] [joint_trajectory_controller]: No specific joint names are used for command interfaces. Using 'joints' parameter.
[ros2_control_node-1] [INFO] [1706906426.251782064] [joint_trajectory_controller]: Command interfaces are [position] and state interfaces are [position velocity].
[ros2_control_node-1] [INFO] [1706906426.251796175] [joint_trajectory_controller]: Using 'splines' interpolation method.
[ros2_control_node-1] [INFO] [1706906426.253023385] [joint_trajectory_controller]: Controller state will be published at 100.00 Hz.
[ros2_control_node-1] [INFO] [1706906426.255108052] [joint_trajectory_controller]: Action status changes will be monitored at 20.00 Hz.
[spawner-4] [INFO] [1706906426.271808978] [spawner_joint_trajectory_controller]: Configured and activated joint_trajectory_controller
[INFO] [spawner-4]: process has finished cleanly [pid 715312]
[ros2_control_node-1] [INFO] [1706906426.411305228] [controller_manager]: Loading controller 'io_and_status_controller'
[spawner-6] [INFO] [1706906427.137736754] [spawner_io_and_status_controller]: Loaded io_and_status_controller
[ros2_control_node-1] [INFO] [1706906427.141101002] [controller_manager]: Loading controller 'speed_scaling_state_broadcaster'
[ros2_control_node-1] [INFO] [1706906427.167567769] [speed_scaling_state_broadcaster]: Loading UR SpeedScalingStateBroadcaster with tf_prefix:
[ros2_control_node-1] [INFO] [1706906427.175412013] [controller_manager]: Configuring controller 'io_and_status_controller'
[spawner-7] [INFO] [1706906427.176480254] [spawner_speed_scaling_state_broadcaster]: Loaded speed_scaling_state_broadcaster
[ros2_control_node-1] [INFO] [1706906427.178482699] [io_and_status_controller]: Configure UR gpio controller with tf_prefix:
[ros2_control_node-1] [INFO] [1706906427.178608226] [io_and_status_controller]: Configure UR gpio controller with tf_prefix:
[ros2_control_node-1] [INFO] [1706906427.183068087] [io_and_status_controller]: Configure UR gpio controller with tf_prefix:
[ros2_control_node-1] [INFO] [1706906427.183292831] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.233391079] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.283589340] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.333781622] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.383984036] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.434218946] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.484433451] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.534540609] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.584670336] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.634863129] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.685015317] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.735202242] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.785384527] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.835574461] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.885735319] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.935982005] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906427.986236780] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.036456890] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.086720046] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.136925965] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.187056170] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.237196010] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.287371549] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.337539805] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.387681253] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.437795259] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.487926659] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.538053473] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.588141403] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.638276627] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.688455973] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.738627224] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.788794204] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.839022163] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.889242401] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.939472269] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906428.989698364] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.039878357] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.090109748] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.140311410] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.190518069] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.240732717] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.290908621] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.341093918] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.391334814] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.441538159] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.491751209] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.541994951] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.592228520] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.642541382] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.692763994] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.743008576] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.793179751] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.843329316] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.893461427] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.943548908] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906429.993704733] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906430.043853393] [io_and_status_controller]: Waiting for system interface to initialize...
[ros2_control_node-1] [INFO] [1706906430.094085304] [io_and_status_controller]: Waiting for system interface to initialize...

I am able to successfully run it when I use a real robot, but when I want to work on it in simulation with the use_fake_hardware flag and a fake IP, I run into the above issue.
I'd appreciate help on the same.

@ShahhhVihaan Do you run Humble or Iron / Rolling? use_fake_hardware has been renamed to use_mock_hardware. The output you've posted seems to be trying to start a real driver instance, which obviously cannot connect to a robot with the IP yyy.yyy.yyy.yyy
@francescosemeraro Depending on what your problem exactly looks like, this could be related to #869 and its "improvement" in #919 if that only happens sporadically.

@fmauch Sorry, for not responding.
I have the same issue when I use use_mock_hardware.
rtc2@rtc2:~/Projects/cram_ws$ ros2 launch ur_robot_driver ur_control.launch.py ur_type:=ur3 robot_ip:=yyy.yyy.yyy.yyy use_mock_hardware:=true initial_joint_controller:=joint_trajectory_controller launch_rviz:=false
[INFO] [launch]: All log files can be found below /home/rtc2/.ros/log/2024-02-23-13-40-05-649441-rtc2-460909
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [dashboard_client-2]: process started with pid [460914]
[INFO] [controller_stopper_node-3]: process started with pid [460916]
[INFO] [ur_ros2_control_node-1]: process started with pid [460912]
[INFO] [urscript_interface-4]: process started with pid [460918]
[INFO] [robot_state_publisher-5]: process started with pid [460920]
[INFO] [spawner-6]: process started with pid [460922]
[INFO] [spawner-7]: process started with pid [460924]
[INFO] [spawner-8]: process started with pid [460926]
[INFO] [spawner-9]: process started with pid [460956]
[INFO] [spawner-10]: process started with pid [460975]
[INFO] [spawner-11]: process started with pid [460978]
[controller_stopper_node-3] [INFO] [1708713606.540112600] [Controller stopper]: Waiting for switch controller service to come up on controller_manager/switch_controller
[robot_state_publisher-5] [INFO] [1708713606.546995577] [robot_state_publisher]: got segment base
[robot_state_publisher-5] [INFO] [1708713606.547100077] [robot_state_publisher]: got segment base_link
[robot_state_publisher-5] [INFO] [1708713606.547107622] [robot_state_publisher]: got segment base_link_inertia
[robot_state_publisher-5] [INFO] [1708713606.547111340] [robot_state_publisher]: got segment flange
[robot_state_publisher-5] [INFO] [1708713606.547114758] [robot_state_publisher]: got segment forearm_link
[robot_state_publisher-5] [INFO] [1708713606.547118067] [robot_state_publisher]: got segment ft_frame
[robot_state_publisher-5] [INFO] [1708713606.547121243] [robot_state_publisher]: got segment shoulder_link
[robot_state_publisher-5] [INFO] [1708713606.547124501] [robot_state_publisher]: got segment tool0
[robot_state_publisher-5] [INFO] [1708713606.547127631] [robot_state_publisher]: got segment upper_arm_link
[robot_state_publisher-5] [INFO] [1708713606.547130849] [robot_state_publisher]: got segment world
[robot_state_publisher-5] [INFO] [1708713606.547133969] [robot_state_publisher]: got segment wrist_1_link
[robot_state_publisher-5] [INFO] [1708713606.547137118] [robot_state_publisher]: got segment wrist_2_link
[robot_state_publisher-5] [INFO] [1708713606.547140353] [robot_state_publisher]: got segment wrist_3_link
[ur_ros2_control_node-1] [WARN] [1708713606.554768154] [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.
[ur_ros2_control_node-1] text not specified in the tf_prefix tag
[ur_ros2_control_node-1] [INFO] [1708713606.555180194] [resource_manager]: Loading hardware 'ur3'
[ur_ros2_control_node-1] [INFO] [1708713606.556714142] [resource_manager]: Initialize hardware 'ur3'
[ur_ros2_control_node-1] [INFO] [1708713606.556768086] [resource_manager]: Successful initialization of hardware 'ur3'
[ur_ros2_control_node-1] [WARN] [1708713606.556895607] [controller_manager]: [Deprecated]: Automatic activation of all hardware components will not be supported in the future anymore. Use hardware_spawner instead.
[ur_ros2_control_node-1] [INFO] [1708713606.556925444] [resource_manager]: 'configure' hardware 'ur3'
[ur_ros2_control_node-1] [INFO] [1708713606.556930686] [resource_manager]: Successful 'configure' of hardware 'ur3'
[ur_ros2_control_node-1] [INFO] [1708713606.556950722] [resource_manager]: 'activate' hardware 'ur3'
[ur_ros2_control_node-1] [INFO] [1708713606.556956771] [URPositionHardwareInterface]: Starting ...please wait...
[ur_ros2_control_node-1] [INFO] [1708713606.556966587] [URPositionHardwareInterface]: Initializing driver...
[dashboard_client-2] [ERROR] [1708713606.560844972] [UR_Client_Library:]: Failed to get address for yyy.yyy.yyy.yyy:29999
[ur_ros2_control_node-1] [ERROR] [1708713606.570352206] [UR_Client_Library:]: Failed to get address for yyy.yyy.yyy.yyy:30002
[ur_ros2_control_node-1] [ERROR] [1708713606.584159461] [UR_Client_Library:]: Failed to get address for yyy.yyy.yyy.yyy:30004
[ur_ros2_control_node-1] [ERROR] [1708713606.584220401] [UR_Client_Library:]: Attempt to write on a non-connected socket
[ur_ros2_control_node-1] [ERROR] [1708713606.584224969] [UR_Client_Library:]: Sending RTDE pause command failed!
[ur_ros2_control_node-1] [FATAL] [1708713606.584248613] [URPositionHardwareInterface]: Failed to connect to robot. Please check if the robot is booted and connected.
[ur_ros2_control_node-1] [INFO] [1708713606.584262912] [resource_manager]: Failed to 'activate' hardware 'ur3'
[controller_stopper_node-3] [INFO] [1708713606.587695947] [Controller stopper]: Service available
[controller_stopper_node-3] [INFO] [1708713606.587737346] [Controller stopper]: Waiting for list controllers service to come up on controller_manager/list_controllers
[controller_stopper_node-3] [INFO] [1708713606.587752153] [Controller stopper]: Service available
[ur_ros2_control_node-1] [WARN] [1708713606.590110232] [controller_manager]: Could not enable FIFO RT scheduling policy
[ur_ros2_control_node-1] [INFO] [1708713607.391877874] [controller_manager]: Loading controller 'joint_state_broadcaster'
[ur_ros2_control_node-1] [INFO] [1708713607.400164024] [controller_manager]: Loading controller 'io_and_status_controller'
[spawner-7] [INFO] [1708713607.414244749] [spawner_joint_state_broadcaster]: Loaded joint_state_broadcaster
[ur_ros2_control_node-1] [INFO] [1708713607.415173604] [controller_manager]: Loading controller 'forward_position_controller'
[ur_ros2_control_node-1] [INFO] [1708713607.423027611] [controller_manager]: Loading controller 'speed_scaling_state_broadcaster'
[ur_ros2_control_node-1] [INFO] [1708713607.427618187] [speed_scaling_state_broadcaster]: Loading UR SpeedScalingStateBroadcaster with tf_prefix:
[ur_ros2_control_node-1] [INFO] [1708713607.431441800] [controller_manager]: Loading controller 'force_torque_sensor_broadcaster'
[spawner-8] [INFO] [1708713607.431944268] [spawner_io_and_status_controller]: Loaded io_and_status_controller
[spawner-11] [INFO] [1708713607.436009567] [spawner_forward_position_controller]: Loaded forward_position_controller
[ur_ros2_control_node-1] [INFO] [1708713607.439141174] [controller_manager]: Loading controller 'joint_trajectory_controller'
[ur_ros2_control_node-1] [WARN] [1708713607.445574804] [joint_trajectory_controller]: [Deprecated]: "allow_nonzero_velocity_at_trajectory_end" is set to true. The default behavior will change to false.
[spawner-9] [INFO] [1708713607.446571746] [spawner_speed_scaling_state_broadcaster]: Loaded speed_scaling_state_broadcaster
[ur_ros2_control_node-1] [INFO] [1708713607.447921275] [controller_manager]: Configuring controller 'joint_state_broadcaster'
[ur_ros2_control_node-1] [INFO] [1708713607.447998492] [joint_state_broadcaster]: 'joints' or 'interfaces' parameter is empty. All available state interfaces will be published
[spawner-10] [INFO] [1708713607.451563479] [spawner_force_torque_sensor_broadcaster]: Loaded force_torque_sensor_broadcaster
[ur_ros2_control_node-1] [INFO] [1708713607.455683833] [controller_manager]: Configuring controller 'io_and_status_controller'
[spawner-6] [INFO] [1708713607.460536916] [spawner_joint_trajectory_controller]: Loaded joint_trajectory_controller
[ur_ros2_control_node-1] [INFO] [1708713607.462994398] [controller_manager]: Configuring controller 'forward_position_controller'
[ur_ros2_control_node-1] [INFO] [1708713607.463629734] [forward_position_controller]: configure successful
[ur_ros2_control_node-1] [INFO] [1708713607.471423509] [controller_manager]: Configuring controller 'speed_scaling_state_broadcaster'
[ur_ros2_control_node-1] [INFO] [1708713607.471508424] [speed_scaling_state_broadcaster]: Publisher rate set to : 100.0 Hz
[ur_ros2_control_node-1] [INFO] [1708713607.479071560] [controller_manager]: Configuring controller 'force_torque_sensor_broadcaster'
[ur_ros2_control_node-1] [INFO] [1708713607.487432126] [controller_manager]: Configuring controller 'joint_trajectory_controller'
[ur_ros2_control_node-1] [INFO] [1708713607.487599917] [joint_trajectory_controller]: No specific joint names are used for command interfaces. Using 'joints' parameter.
[ur_ros2_control_node-1] [INFO] [1708713607.487620529] [joint_trajectory_controller]: Command interfaces are [position] and state interfaces are [position velocity].
[ur_ros2_control_node-1] [INFO] [1708713607.487630297] [joint_trajectory_controller]: Using 'splines' interpolation method.
[ur_ros2_control_node-1] [INFO] [1708713607.488490901] [joint_trajectory_controller]: Controller state will be published at 100.00 Hz.
[ur_ros2_control_node-1] [INFO] [1708713607.489594536] [joint_trajectory_controller]: Action status changes will be monitored at 20.00 Hz.
[spawner-7] [INFO] [1708713607.511410447] [spawner_joint_state_broadcaster]: Configured and activated joint_state_broadcaster
[ur_ros2_control_node-1] [INFO] [1708713607.518871422] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713607.568963256] [io_and_status_controller]: Waiting for system interface to initialize...
[INFO] [spawner-11]: process has finished cleanly [pid 460978]
[ur_ros2_control_node-1] [INFO] [1708713607.619123012] [io_and_status_controller]: Waiting for system interface to initialize...
[INFO] [spawner-7]: process has finished cleanly [pid 460924]
[ur_ros2_control_node-1] [INFO] [1708713607.669278126] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713607.719417728] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713607.769587961] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713607.819820356] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713607.870062637] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713607.920325050] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713607.970551835] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.020793474] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.071041034] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.121250417] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.171474011] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.221583715] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.271692186] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.321873376] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.372107681] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.422284456] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.472483974] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.522743798] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.572974625] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.623196084] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.673428605] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.723650997] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.773804198] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.823942797] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.874175923] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.924393946] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713608.974542213] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713609.024727727] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713609.074977390] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713609.125194590] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713609.175447149] [io_and_status_controller]: Waiting for system interface to initialize...
[ur_ros2_control_node-1] [INFO] [1708713609.225652919] [io_and_status_controller]: Waiting for system interface to initialize...

I'd appreciate your help. I've been working directly on the real robot but it would be incredibly helpful if I can validate things in simulation.

Closing this. The OP's problem should have been fixed in #920 and the issue by @ShahhhVihaan is not reproducible. I assume that the description is being used from the wrong branch?


Denote strategies that do not require prior registration

It would be nice if https://github.com/opauth/opauth/wiki/List-of-strategies make a distinction of which login strategies require prior registration to use that service.
In my open source PHP project, I can include Open ID Google and Yahoo login and users can use that immediately. However Facebook is a different experience and requires my users to set this up with Facebook before beginning.

Would a pull request be accepted that fixes this issue?

Closing as there is no interest in a PR for this.


Issue in join queries

Hello,
I tried to execute the below three queries using dataframe_sql. but only first and third are working, ideally, all three should work as there in proper SQL format. Its saying error as - "Joined tables have overlapping names: ['pid', 'pdh', 'enddate', 'dep_head', 'serialNo']".

SELECT table1.pdh as pdh
FROM table1 as t1
inner join table2 as t2 on (t2.serialNo=t1.serialNo and t2.pdh=t1.pdh)

SELECT table1.pdh as pdh
FROM table1 as t1
inner join table2 as t2 on (t2.serialNo=t1.serialNo and t2.pdh=t1.pdh)
where s2 < '100'

SELECT *
FROM table1 as t1
inner join table2 as t2 on (t2.serialNo=t1.serialNo and t2.pdh=t1.pdh)
where s2 < '100'

@itsds Thanks for bring this up, I'll look into it!


functions calling returning an undocumented multi_tool_use.parallel case

Confirm this is a Node library issue and not an underlying OpenAI API issue

[X] This is an issue with the Node library

Describe the bug
Hello,
I'm encountering an undocumented use of the function calling feature, using the new assistant/threads features via the SDK.
In some occasions (happened already 3x today), the function calling is returning a structure as in the screenshot below.
Please note that this behavior is random. Not happening 100% of the time, so maybe related to an underlying issue, but no-one from openai has replied to the initial thread.

Any knowledge of this ?
Thanks
Original thread in the community:
https://community.openai.com/t/model-tries-to-call-unknown-function-multi-tool-use-parallel/490653/6
To Reproduce
Seems like related to complex calls, the model looking like it wants to parallelize function call executions.
Code snippets
No response
OS
macOS
Node version
Node v21.1.0
Library version
openai v4.12.4

I dont really get why both exists, but you tried with runTools ?

Thanks for reporting, I'll pass it along.
I'm going to go ahead and close this issue because it's not a bug in the TypeScript library.


Moving config to firebase storage

Is your feature request related to a problem? Please describe.
The config file is currently stored in the cloud fire store, when the config file exceeds the max allowed 1,048,576 bytes, it throws error.
Describe the solution you'd like
Moving config file to storage, like sequences.
Additional context
This error happens when we are developing an experiment that has 1400 questions.

Prefix storage folders with dev- or prod-

Closed via #387


ARROW-17764: [CI][C++] "#include " is missing

https://github.com/ursacomputing/crossbow/actions/runs/3073442125/jobs/4965573117#step:5:8420
FAILED: src/arrow/flight/sql/CMakeFiles/arrow_flight_sql_objlib.dir/sql_info_internal.cc.o
/usr/bin/c++ .../arrow/cpp/src/arrow/flight/sql/sql_info_internal.cc
In file included from /arrow/cpp/src/arrow/flight/sql/sql_info_internal.h:20,
                 from /arrow/cpp/src/arrow/flight/sql/sql_info_internal.cc:18:
/arrow/cpp/src/arrow/flight/sql/types.h:899:8: error: 'optional' in namespace 'std' does not name a template type
  899 |   std::optional<std::string> catalog;
      |        ^~~~~~~~
/arrow/cpp/src/arrow/flight/sql/types.h:29:1: note: 'std::optional' is defined in header '<optional>'; did you forget to '#include <optional>'?
   28 | #include "arrow/type_fwd.h"
  +++ |+#include <optional>
   29 |
/arrow/cpp/src/arrow/flight/sql/types.h:901:8: error: 'optional' in namespace 'std' does not name a template type
  901 |   std::optional<std::string> db_schema;
      |        ^~~~~~~~
/arrow/cpp/src/arrow/flight/sql/types.h:901:3: note: 'std::optional' is defined in header '<optional>'; did you forget to '#include <optional>'?
  901 |   std::optional<std::string> db_schema;
      |   ^~~

@github-actions crossbow submit verify-rc-source-cpp-linux-ubuntu-22.04-amd64 verify-rc-source-ruby-linux-ubuntu-22.04-amd64


YOUKU Download failed

use youtube-dl 2017.04.28
Microsoft Windows [版本 6.1.7601]
版权所有 (c) 2009 Microsoft Corporation。保留所有权利。
C:\Users\Administrator>youtube-dl http://v.youku.com/v_show/id_XMjczMzQyOTk4OA==
.html?spm=a2hzp.8244740.0.0&from=y1.7-1.1
[youku] XMjczMzQyOTk4OA: Downloading JSON metadata
[download] Downloading playlist: 10 强者不屈,勇者无惧
[youku] playlist 10 强者不屈,勇者无惧: Collected 31 video ids (downloading 31 of
them)
[download] Downloading video 1 of 31
[download] Destination: 10 强者不屈,勇者无惧-XMjczMzQyOTk4OA_part1.flv
[download] 100% of 46.91MiB in 00:11
[download] Downloading video 2 of 31
[download] Destination: 10 强者不屈,勇者无惧-XMjczMzQyOTk4OA_part2.flv
[download] 100% of 42.52MiB in 00:11
[download] Downloading video 3 of 31
[download] Destination: 10 强者不屈,勇者无惧-XMjczMzQyOTk4OA_part3.flv
[download] 100% of 56.58MiB in 00:15
[download] Downloading video 4 of 31
ERROR: unable to download video data: HTTP Error 404: Not Found
'from' 不是内部或外部命令，也不是可运行的程序
或批处理文件。
C:\Users\Administrator>

You need to enclose the URL in double quotes. For example:
youtube-dl "http://v.youku.com/v_show/id_XMjczMzQyOTk4OA==.html?spm=a2hzp.8244740.0.0&from=y1.7-1.1"

See https://github.com/rg3/youtube-dl/blob/master/README.md#video-url-contains-an-ampersand-and-im-getting-some-strange-output-1-2839-or-v-is-not-recognized-as-an-internal-or-external-command

Thanks so much for your help! But it still didn't work.There are 31 parts of videos in total,but only the first one，second one and third one can be downloaded.
This situation started from last week.Before last week，all the videos are available.
Thank you again for your kindness!
Microsoft Windows [版本 6.1.7601]
版权所有 (c) 2009 Microsoft Corporation。保留所有权利。
C:\Users\Administrator>youtube-dl "http://v.youku.com/v_show/id_XMjczMzQyOTk4OA==.html?spm=a2hzp.8244740.0.0&from=y1.7-1.1"
[youku] XMjczMzQyOTk4OA: Downloading JSON metadata
[download] Downloading playlist: 10 强者不屈,勇者无惧
[youku] playlist 10 强者不屈,勇者无惧: Collected 31 video ids (downloading 31 of
them)
[download] Downloading video 1 of 31
[download] Destination: 10 强者不屈,勇者无惧-XMjczMzQyOTk4OA_part1.flv
[download] 100% of 46.91MiB in 00:10
[download] Downloading video 2 of 31
[download] Destination: 10 强者不屈,勇者无惧-XMjczMzQyOTk4OA_part2.flv
[download] 100% of 42.52MiB in 00:10
[download] Downloading video 3 of 31
[download] Destination: 10 强者不屈,勇者无惧-XMjczMzQyOTk4OA_part3.flv
[download] 100% of 56.58MiB in 00:13
[download] Downloading video 4 of 31
ERROR: unable to download video data: HTTP Error 404: Not Found
C:\Users\Administrator>

I have the membership of Youku, is it possible that I download videos with this software？

@saku1119  See https://pan.baidu.com/s/1dFILEl7

If you want to download youku videos with youtube-dl, you can export cookies.txt via browser extensions and feed it to youtube-dl:
youtube-dl -v (the URL) --cookies cookies.txt

to ckz1211， Thank you so much, it works！
to yan12125，Thank you for your kind reply！But it's shown in system that‘http.cookiejar.loaderror’can not be downloaded.
Microsoft Windows [版本 6.1.7601]
版权所有 (c) 2009 Microsoft Corporation。保留所有权利。
C:\Users\Administrator>youtube-dl -v "http://v.youku.com/v_show/id_XMjczMzQzMDA2
NA==.html?from=zpdvip.001" --cookies cookies.txt
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'http://v.youku.com/v_show/id_XMjczMzQzMDA2NA=
=.html?from=zpdvip.001', '--cookies', 'cookies.txt']
Traceback (most recent call last):
File "main.py", line 19, in
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpagq0np72\bu
ild\youtube_dl_init_.py", line 465, in main
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpagq0np72\bu
ild\youtube_dl_init_.py", line 432, in _real_main
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpagq0np72\bu
ild\youtube_dl\YoutubeDL.py", line 388, in init
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpagq0np72\bu
ild\youtube_dl\YoutubeDL.py", line 2189, in _setup_opener
File "C:\Python\Python34\lib\http\cookiejar.py", line 1781, in load
File "C:\Python\Python34\lib\http\cookiejar.py", line 2005, in _really_load
http.cookiejar.LoadError: 'cookies.txt' does not look like a Netscape format coo
kies file
C:\Users\Administrator>

to ckz1211 Thank you so much, it works！but lost part3 and part16.
to yan12125 Thank you for your kind reply！it works perfectly!


Hot-reloader was not disabled for production build, causing the hot-reloader still working in production

JSPM is an important part of my daily JS dev. workflow. It works greatly for my work except that the duration of refreshing my app takes a long time to load into the browser (in dev/debugging phase). To mitigate this headache instead of trying Webpack, I decided to try this lib.
The lib setup and run up exactly as the readme states, the outcome is awesome as well, so the speed of dev/debugging is really a snap. But, after execute "jspm bundle-sfx", and release the bundle into the production, the hot-reloader are still working, which is not as expected as stated by the wiki:
"At the top of your es6 code:"
"import 'systemjs-hot-reloader/default-listener.js"
"Maps to empty module on production builds, so no needs for any if statements."
The JSPM bundle CLI used is:
❯ jspm bundle-sfx ./jslib/zy_wf_op/zy_workflow_op ./builds/zy_workflow_op_build.js --minify;
Building the single-file sfx bundle for ./jslib/zy_wf_op/zy_workflow_op...
ok   Built into builds/zy_workflow_op_build.js with source maps, minified, mangled.
Any hints to resolve?
Thanks!

@Simon-Li This should be mapping to @empty in production and node. Still having this issue?

https://github.com/alexisvincent/systemjs-hot-reloader/releases/tag/v1.0.0 maps to @empty


Add CSS Grid Layout Module Level 3 (Masonry!)

https://drafts.csswg.org/css-grid-3/
Probably early and likely will come via MDN, but keeping track 0:-)

https://www.smashingmagazine.com/native-css-masonry-layout-css-grid/

https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_Layout/Masonry_Layout

Indeed available via MDN: https://caniuse.com/?search=masonry
Currently in two entries:

https://caniuse.com/mdn-css_properties_masonry
https://caniuse.com/mdn-css_properties_masonry-auto-flow

Indeed, this is covered by MDN data (via mdn/browser-compat-data#7249), but it appears there may be more work to be done.
grid-template-rows: masonry is covered here:
https://caniuse.com/mdn-css_properties_grid-template-rows_masonry
masonry-auto-flow (as mentioned above) is covered here:
https://caniuse.com/mdn-css_properties_masonry-auto-flow
But grid-template-columns: masonry is missing, and mdn/browser-compat-data#9078 suggests that it may actually be (incorrectly) covered by this entry:
https://caniuse.com/mdn-css_properties_masonry

https://webkit.org/blog/13839/release-notes-for-safari-technology-preview-163/:

Masonry Layout

Enabled Masonry layout by default (258694@main, 259308@main)
Added the initial support for align-tracks and justify-tracks (258544@main)


Save resampled climates from KCS diagnostic local_resampling.py

Description
Extends the KCS recipe to also output the actual resampled climates.
https://docs.esmvaltool.org/en/latest/recipes/recipe_kcs.html
It's my first attempt at a pull request, I don't know how to check the automatic checks yet...
Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[x] 🛠 This pull request has a descriptive title
[x] 🛠 Code is written according to the code quality guidelines
[x] 🛠 Documentation is available
[x] 🛠 Tests run successfully
[x] 🛠 The list of authors is up to date
[x] 🛠 Any changed dependencies have been added or removed correctly
[x] 🛠 All checks below this pull request were successful

New or updated recipe/diagnostic

[ ] 🧪 Recipe runs successfully
[ ] 🧪 Recipe is well documented
[ ] 🧪 Figure(s) and data look as expected from literature
[x] 🛠 Provenance information has been added

To help with the number of pull requests:

🙏 We kindly ask you to review two other open pull requests in this repository

Hey Emma,
Welcome and congratulations on your first PR! I'll try to find some time soon to do a review. One thing I noticed already is that you added daniels_emma as an author, but I don't think you added yourself to config_references as well, did you?

Hi Peter, I'm a bit overwhelmed with this whole process. Added it now.

@esmvalbot please run recipe_kcs.yml

Hi, I haven't been able to see the generated output. Is there something I need to know? It looks like a cool feature to test recipes.

Hi, I haven't been able to see the generated output. Is there something I need to know? It looks like a cool feature to test recipes.

The bot is really cool but today it's just very slow, or there is a queue, or something like that. It just hasn't run yet...

The bot failed with a merge problem due to different types. This issue has cropped up before and is discussed in https://github.com/ESMValGroup/ESMValTool/discussions/2218#discussioncomment-992288 and links therein.

@Emmadd Release v2.5 is approaching quickly (the feature freeze will be on 2022-02-21). Since this pull request is marked for v2.5, could you briefly comment if you further intend to include this in the new release and/or if you are facing any problems with it? Thanks!!


ngs-data fixes

updates API url / access
removes redundant teamlogos file
moves update_ngs.R to exec/ so we can use pkgload
splits exec/update_ngs.R into one file per workflow step to avoid envvar handling the split logic

https://github.com/nflverse/ngs-data/actions/runs/11201538177


CLIENTS-297: TLS/Auth now handles RpbErrorResp

If security isn't enabled, or auth fails, the RiakConnection now
emits a 'connectFailed' with the appropriate error message and
destroys itself. The error message is propagated up to the command's
onError() callback.

:+1:


"Măgurele" is listed in the drop-down menu.

Description:
"Măgurele" is listed in the drop-down menu alongside its corresponding county according to the law
Precondition:
The website is up an running.

Step 1
Type "Măgurele" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Măgurele, PRAHOVA".


Remove syscall usage

Recently Apple has begun cracking down on apps that appear to be trying to build a fingerprint of the user device to evade privacy rules.  The code they are targeting is also used by KSCrash to add metadata to the crash header, in many ways a crash header is similar to a fingerprint in that you want as much meta data as possible.
To reduce our risk of getting flagged by app store review we are removing this syscall usage from our SDKs fork of the KSCrash repo.

Hey this looks like a good idea! Are you going to open a new PR?

Hey this looks like a good idea! Are you going to open a new PR?

Hmm, I had intended this for our fork since I wasn't sure everybody would want such a change made.  Maybe for the public repo having this change be behind a define might be best, just so folks using it in dev environment can still get full headers?


patches: Update for 76.0.3809.87

@Eloston I removed most of the Debian patches this time, as you suggested a while back.

is the gcc-9 patch really no longer needed?

@jstkdng It is not, see the patches included in the original chromium package for Arch Linux.

@xsmile yeah, just checked. I'll add the changes to my repo.

It seems Eloston hasn't updated the tags in his repo, so right now this PKGBUILD won't compile.

@jstkdng Just added a tag.


Does support spark sql

As we all know, caravel supports druid.
But in my project, we use spark mllib and spark sql. So I want caravel support spark sql.
Does caravel support spark sql? If not, how the druid integrate with hortonworks hdp?

Looks like a dup of https://github.com/airbnb/caravel/issues/241

I have replied to question on #241 since I was able to successfully connect caravel to spark sql using dropbox/pyhive.


Failed to prove my program with stone-cli

I'm was trying to prove using cairo1-run + cpu_air_prover.
Bug on bug. I tried your tool and didn't worked either.
Mentioned here:
https://github.com/lambdaclass/cairo-vm/issues/1889#issuecomment-2525065749
Scroll up for more context.
I ran
stone-cli prove \
  --prover_config_file $CFG_AND_PARAMS_DIR/cpu_air_prover_config.json  \
  --cairo_program target/release/$PROGRAM_NAME.sierra.json \
  --program_input "[650157136941007917207724121471813482783483983289688285320161307177215463403<PHONE_NUMBER>808460179723299787189716707852181277595105475126938070374837146371]" \
  --layout all-cairo \
  --output $PROOF_OUTPUT_DIR/proof.json

And used the main branch of the repo

Marking this as duplicate of https://github.com/zksecurity/stone-cli/issues/29. Please reopen if I'm wrong.


feat: Use code indentation of 2

As discussed on the dev call...
No religious view (generally I find 4 good in many langs), though I do think with compact queries, 2 is very elegant

Note that we can use .editorconfig to enforce indent size to all .prql files. (And check by MegaLinter on CI)

Note that we can use .editorconfig to enforce indent size to all .prql files. (And check by MegaLinter on CI)

And hopefully a pre-commit step of prqlc fmt!


Make CLI for testing the compliance with agent protocol

I added an argument for url
Moved everything under test command
Cleaned up few things

Nice! I think the last thing we're missing is just the mention on how to use the CLI in the readme

I think we can merge this @jakubno if there's nothing more on your end. What do you think?

Thinking about it a bit more - maybe we should mention the CLI in the main readme as well. This is something even JS/TS users will want to use. That's why I'm a bit worried that requiring from users to set up poetry and virtual python env will be pain. Folks from JS/TS world don't know this.

Folks from JS/TS world don't know this.

Could there be a way to replicate it natively to JS/TS? Like an npx tool? If I'm not mistaken, it could even be just a wrapper for the python client with a script that sets everything up.

Sure, I will mention it there as well.

That's why I'm a bit worried that requiring from users to set up poetry and virtual python env will be pain. Folks from JS/TS world don't know this.
I will rewrite the docs, probably it isn't clear. You only need to run

pip install agent-protocol

then you can run
agent-protocol test -u localhost:8000

python and therefore pip are by default on Mac / Linux, the only problem could be Windows without python installed.
But we can add the same functionality to the JS package as well, it should be quite easy

I think this is good DX. Ultimately I don't think it matters if you need to run pip install or npm i (we might want to have brew installation in the future). The point is that you can now just run agent-protocol and it'll work without anything else.
Merging and closing. Thanks!


Handle that normalizing leads to an empty query

@arnej27959 please review

this looks ok as far as it goes, but only helps in the most simple case, right?

but only helps in the most simple case

I don't think it is a problem in any other case.


NLB on AWS EKS with UDP-only targets, and IP target type behaves strangely with Cilium enabled

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
When I create a NLB on EKS with UDP-only targets, and use target-type: ip instead of instance, pods on some nodes get UDP packets from Load Balancer, but their response never reaches back the sender.
This only happens on some nodes, pods on other nodes can reply to the sender just fine.
When I delete and recreate AWS instances backing the worker nodes in the cluster, again this only happens on some nodes, and other nodes work just fine (it's just the set of working/broken is different now).
When I uninstall Cilium, and reinstall AWS CNI, all pods can receive UDP packets and reply to the originator. When I reinstall Cilium (deleting AWS CNI and doing "cilium install"), the pattern of some nodes not being able to reply reoccurs.
Cilium Version
cilium-cli: v0.10.6 compiled with go1.18.1 on linux/amd64
cilium image (default): v1.10.11
cilium image (stable): v1.11.5
cilium image (running): v1.11.3
Kernel Version
5.4.190-107.353.amzn2.x86_64
Kubernetes Version
Server Version: version.Info{Major:"1", Minor:"21+", GitVersion:"v1.21.9-eks-0d102a7", GitCommit:"eb09fc479c1b2bfcc35c47416efb36f1b9052d58", GitTreeState:"clean", BuildDate:"2022-02-17T16:36:28Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
(file upload failed)
Relevant log output
No response
Anything else?
To repro:  make sure you have 7+ nodes in your cluster create echo server:
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    test-app: echo-udp
  name: echo-udp
spec:
  replicas: 15
  selector:
    matchLabels:
      test-app: echo-udp
  template:
    metadata:
      labels:
        test-app: echo-udp
    spec:
      containers:
      - name: echo
        image: n0r1skcom/echo
---
apiVersion: v1
kind: Service
metadata:
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip
    service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing
    service.beta.kubernetes.io/aws-load-balancer-type: external
  labels:
    test-app: echo-udp
  name: echo-udp
spec:
  type: LoadBalancer
  ports:
  - name: echo
    port: 3333
    protocol: UDP
    targetPort: 3333
  selector:
    test-app: echo-udp

run in loop on your laptop:
for i in $(seq 1 1000); do echo $i; echo $i | nc -w 1 -u <IP-of-NLB> 3333 | grep Hostname || echo FAIL FAIL FAIL; sleep 1; done

(try all IPs returned by NLB's DNS record, I found that some fail more often than others)
and in your cluster, do
kubectl logs -f -l test-app=echo-udp --max-log-requests 15 | grep -A 4 UDP

to observe how all UDP packets are reaching the pods.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I don't how to investigate it without sysdump and traces of each hop.

https://drive.google.com/file/d/1TmWZ72rw5cTFEx9pOelAR9jOq5Y3T4mL/view?usp=sharing
sorry, I couldn't upload it to github.
You might be able to repro it using my deployment/service above. I reproed it in multiple separate EKS clusters.

(I uploaded sysdump above)

cc @brb

I still need to know what packet and hops.

Sorry, I'm not sure what else you need, exactly. Can you be more specific? I'll be happy to provide it.


Windows - reload replaced/updated todo.txt

Hi @ransome1,
I am a simple user, not a coder. I discovered your Sleek program for Windows a few days ago. I really like the look and feel of it - nicely done!
I am using SimpleTask (Cloudless) on Android with SyncThing to keep shared files updated between laptop (Windows), phone (Android) and a tablet (Android).
SyncThing replaces the todo.txt file that is currently open by the ToDo applications. This does not seem to be a problem for the Android apps, as they apparently simply reload the todo.txt on the fly or I can use a menu option to refresh the currently open file.
Sleek falls back to its start screen once the open todo.txt is replaced. It does reload the updated file eventually but it took from 30 to 90+ seconds during my tests and a few times it did not reload the todo.txt at all and simply stayed at the start screen.
In case I am not the only one with this issue, can the interval of file update checks be increased? Or a third button be added to the start screen to quickly refresh the most recently open todo.txt?
Thank you.

Hi @D3JA5U.
That is interesting, because I too am using Syncthing and am not experiencing that problem. But let me see, if I can setup the file watcher to to wait a bit, before trying to reload the file. That should solve this problem.
If everything goes well, this will be part of the next release.
If that doesn't solve the problem, maybe the button you mentioned might be a solution. Then sleek would not reload itself, but simply show a reload button, once a change on the file has been detected.

Hi @D3JA5U.
That is interesting, because I too am using Syncthing and am not experiencing that problem. But let me see, if I can setup the file watcher to to wait a bit, before trying to reload the file. That should solve this problem.
If everything goes well, this will be part of the next release.
If that doesn't solve the problem, maybe the button you mentioned might be a solution. Then sleek would not reload itself, but simply show a reload button, once a change on the file has been detected.

Thank you for your quick response.
If it is working for you it could be an issue on my system only.
I noticed that once Sleek falls back to its start screen and I want to (re-) open my todo file it always starts at the %user% folder, not the one where the previously used todo.txt resides but I assume that is working as intended.
Should not make a difference but I have the todo.txt on a second internal hard drive on the laptop. Will test this later by moving everything to C:

Thank you for your quick response.
If it is working for you it could be an issue on my system only.
I noticed that once Sleek falls back to its start screen and I want to (re-) open my todo file it always starts at the %user% folder, not the one where the previously used todo.txt resides but I assume that is working as intended.
Should not make a difference but I have the todo.txt on a second internal hard drive on the laptop. Will test this later by moving everything to C:

@D3JA5U, I implemented a simple interval of 60 seconds, before the file is reread after it has changed. If you like, I'll upload it and you could check, if this solves the problem on your side. I am just not sure about the interval. For the general user experience the shorter the better I guess.
Are you using the exe file from Github's release page?

@D3JA5U, I implemented a simple interval of 60 seconds, before the file is reread after it has changed. If you like, I'll upload it and you could check, if this solves the problem on your side. I am just not sure about the interval. For the general user experience the shorter the better I guess.
Are you using the exe file from Github's release page?

Can I ask you something? When you look at the file in your Explorer and if you then change it in Simpletask, do you actually see it disappear and reemerge in Explorer?

Can I ask you something? When you look at the file in your Explorer and if you then change it in Simpletask, do you actually see it disappear and reemerge in Explorer?

Version 0.6.0 was downloaded from this page. Today I deleted all folders related to Sleek 0.6.0 and the corresponding SyncThing pairs on all devices. I then downloaded version 0.7.0 from this page and I set up new folders and pairs in SyncThing for all devices.
Now, I am happy to report that all is working as expected. Sync is being done within seconds of changing a todo list item on any of my three devices :)
To your question: I actually do not see the todo.txt file disappear/reemerge during sync. Looks like it is not changing in Windows Explorer or it is happening so fast that I can not catch it.

Version 0.6.0 was downloaded from this page. Today I deleted all folders related to Sleek 0.6.0 and the corresponding SyncThing pairs on all devices. I then downloaded version 0.7.0 from this page and I set up new folders and pairs in SyncThing for all devices.
Now, I am happy to report that all is working as expected. Sync is being done within seconds of changing a todo list item on any of my three devices :)
To your question: I actually do not see the todo.txt file disappear/reemerge during sync. Looks like it is not changing in Windows Explorer or it is happening so fast that I can not catch it.

Oh really? I haven't uploaded the version with the timer yet :) Did you change anything on your setup?

Oh really? I haven't uploaded the version with the timer yet :) Did you change anything on your setup?

A newer version of your program and I am running it from C: drive now. I used Sleek to create a new todo.txt file. The previous todo.txt I had started in Notepad++. Maybe it was corrupted somehow but the Android devices had no issues with it. The rest is the same as before.

A newer version of your program and I am running it from C: drive now. I used Sleek to create a new todo.txt file. The previous todo.txt I had started in Notepad++. Maybe it was corrupted somehow but the Android devices had no issues with it. The rest is the same as before.

To close this topic off - likely a glitch/issue on my side. It is working perfectly on 0.7.0. Thank you @ransome1 for swiftly responding to an average Joe trying out your sleek code 👍

To close this topic off - likely a glitch/issue on my side. It is working perfectly on 0.7.0. Thank you @ransome1 for swiftly responding to an average Joe trying out your sleek code 👍


Custom scalar resolvers being shared between schemas

I noticed that subsequent calls to makeExecutableSchema seem to re-use custom resolvers:

const schema1 = makeExectuableSchema({
  typeDefs: `type Query { version: String! }`,
  resolvers: {
    String: CustomString,
    Query: {
      version() {
        return "123.4.56"
      }
    }
  }
})

const schema2 = makeExectuableSchema({
  typeDefs: `type Query { version: String! }`,
  resolvers: {
    Query: {
      version() {
        return "123.4.56"
      }
    }
  }
})

For whatever reason, schema2.__typeMap.String is the same CustomString from schema1!

+1 Cannot use with applyMiddleware and graphql shield :(

issue still present

This is a graphql tools issue, not a graphql issue, due to modification of existing custom or built in scalars when asking implementations via makeExecutableSchema or the underlying addResolvers... method rather than creation of new type.
Will work on fixing this in https://www.npmjs.com/package/graphql-tools-fork

This does not seem easily fixed -- if the default specified scalar type would not be modified, but rather be replaced with a custom type of the same name to add validation, that would initially work.
In fact, that is what you will already get with the latest version of graphql-tools-fork .
However, this schema is inconsistent, as the built in introspection types will still use the original specified graphql version, as those are not modified with healing. This will cause problems if you try to modify the schema by using the graphql extendSchema or the graphql-tools-fork cloneSchema, visitSchema methods.
Seems like this is not supported for a reason, as what you are trying to do is use your own String type that varies by schema, so it should really be separate than the built in.

Closing. Modifying built in graphql types should be not recommended if only for the reason raised by this issue. This is kinda a graphql-js issue after all...


RequestInterface missing getPost

As of zend-mvc Zend\Mvc\Controller\AbstractController, you'll get the RequestInterface as a response of AbstractController::getRequest().
Thus will lead to issues on resolving getPost() in Autocompletions. IMHO, getPost method should be required to any RequestInterface implementing class.
Example
class DummyController extends \Zend\Mvc\Controller\AbstractController
{
    public function dummyAction()
    {
        $request = $this->getRequest();
        $postValues = $request->getPost();
    }
}

The getPost method will work, since \Zend\Http\Request implements it. But Autocompletion wont resolve this, since the return value is RequestInterface.

This is intentional. Zend\Stdlib\RequestInterface is a general purpose request abstraction, and is used as a base for both the HTTP variant as well as those used in zend-mail and zend-console.
If you want IDE autocompletion, you can always put typehints as comments above the variable:
/* @var \Zend\Http\PhpEnvironment\Request */
$request = $this->getRequest();


sourceMappingUrl is relative to /usr/local/google/home/jelbourn/material2/tmp

I got many errors in my systemJsBuilder buildStatic as many of #sourceMappingUrl is relative to this folder.
Please fix it asap ;)

Was a systemjs/builder, sorry for that : https://github.com/systemjs/builder/issues/610


Update Fedora CI legs to test on Fedora 40

Fedora 40 was released on 2024-04-23.  Fedora CI should be updated to test it vs Fedora 39

Superseded by https://github.com/dotnet/source-build/issues/4399


Identify Registration Part 2 Operator Requirements

[ ] Nan and Zoey review registration product vision with Hanna
[ ] Nan will create the workflows for current state #657
[ ] Nan and Zoey will identify the needs and missing features that we may need
[ ] Nan and Zoey create user story assumptions about registration future state
[ ] Zoey document registration future state  requirements and maps out user flows MIRO
[ ] Nan and Zoey create information architecture
[ ] high level understanding on types of workflows needed, given that it needs to fit into a bigger, overall system, disucss with giraffe + devs
[ ] Nan create prototypes to conduct external user validation

cc @hannavovk this is like an epic with individual tasks inside, for now I just created 1 giant ticket for these tasks since we don't have enough information to create ACs and DoD for each of the tasks yet. We can split them out into separate tickets when we have more certainty

Repurposed this ticket to "drafting user scenarios" and closing this ticket because it is Registration Part 2 Requirements is more of an epic. Instead, smaller, individual tickets for each type of feature/workflow will be created.


Prisma introspect not written delete_rule CASCADE  to schema.prisma

Bug description
prisma introspect cannot write delete_rule CASCADE in schema.prisma file

How to reproduce

Create Table used other migration library or .sql file  with relation column rule cascade on delete
after that, run npx prisma introspect
and check the schema.prisma at relation column ON DELETE CASCADE not writen.

Expected behavior
While run npx prisma introspect can write delete_rule in information_schema.REFERENTIAL_CONSTRAINTS

Prisma information
In other migration library

in mysql information_schema.REFERENTIAL_CONSTRAINTS

result after run npx prisma introspect. This file schema.prisma

Environment & setup

OS:  Debian (deepin v20.1)
Database:  MariaDB
Node.js version:  v14.15.3 LTS
Prisma version: v2.15.0
(Other migration) db-migrate: v0.11.12
Express:  v4.16.1

Yes, Prisma schema does not support cascading deletes yet in any way: https://github.com/prisma/prisma/issues/2810


Add MIT Licence

DfE work in the open and MIT is the default license [1]
[1] https://github.com/DFE-Digital/technical-guidance/blob/master/source/documentation/standards/licencing-software-or-code.html.md.erb#L15

@jacksonj04 I started with that but changed it after closer inspection of DfE's guidance, we open sourced in 2020 so I picked that year instead. We could do 2020-2021 but it's not clear to me that that's required

I think we probably have enough updates to justify 2020-2021, but that then just adds a bit of maintenance burden so I really don't feel that strongly.
Ship it!


Quality control: Fix errors

Quality control flagged up a significant number of errors.
https://github.com/obophenotype/c-elegans-gross-anatomy-ontology/blob/master/reports/wbbt-edit-obo-report.tsv
Check the tsv file. But only address this issue after issue 1 is closed!

Will take time to address all those.

duplicate_label resolved.

@raymond91125
You need to run the ODK pipeline first


Updated contained AG Azure Arc instruction steps for accuracy

Modified the "Add the database backup file into the primary instance container" instruction section to include the "-c " option that is present in the example. Also changed the  to  to keep the previous steps consistent with this step in the documentation.

@clayton006 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@grrlgeek please have a look at this and let me know if there are any issues.

#label:"aq-pr-triaged"

#90282


Updating node module based cards is a PAIN

The correct flow seems to be:

git clone url/to/card/repo
npm link to the mother app from the card folder
Start development, restart rails server and rebuild the entire app anytime a change happens.

This is painful because restarting the server and rebuilding take a really long time.
Possible solutions (only tangentially explored):

Add node_modules to watchman's watch-list
Explore Broccoli merge tree. cc @DTrejo on this one.
Make the card modules into proper ember addons. I think those modules will be watched for changes.

cc @egh @mikem

cc @tonywok — @DTrejo

I have a system that works. I think that it should be the way that tahi engines are distributed.
Here is a samle app: https://github.com/egh/example-tahi-engine
Check the code out into engines/. You can install the engine using the task using:
$ rake custom_cards:install_engine[engines/example_tahi_engine]

This design has the following useful properties:

Rails & ember code in the same repo.
Easy installation via a single rake task.
Ember code is rebuilt on change without a restart of rails.
Changes to your ember code are automatically rebuilt without a restart

@egh +1


Hooks are being copied to all projects inside an umbrella

Describe the bug
A hook from one project inside an umbrella project is being copied to the assets folder of the other project in the same umbrella project.
How to reproduce it

Create an umbrella project
Create two web projects ("A" and "B") inside this umbrella project
Create a component with a JavaScript hook on project "A"
Build the project
Check that the hook created in project "A" is also present in "B"

The behavior you expected
The desired behavior is that the hook created on project A do not be copied to project B. Copying all hooks to all projects causes an unnecessary increase of app.js final file size since the most common are components used in project A is not being used in project B.
Your Environment
Phoenix: 1.6.6
Surface: v0.7.0
LiveView: v0.17.6
Elixir: v1.13.2

Fixed in https://github.com/surface-ui/surface/pull/591.


Some examples of use would be really helpful...

Hi,
I've started to use the simple-logstash cookbook for the simple of logstash.
How do you use the cookbook to turn logstash off and on like a service? what is the correct syntax?
I've tried:-
logstash_service "logstash" do
action :enable, :start
end
and it hasn't worked.
How would I specify the location of my configuration file, opt/logstash-1.5.3/conf.d/logstash.conf, in a simple-logstash cookbook resource as well?
Many thanks

Hi,
Take a look at test cookbook for logstash. This is typicall usage:
https://github.com/jsirex/simple-logstash-cookbook/tree/master/test/fixtures/cookbooks/simple-logstash-test

Also, fixed url in readme. Thanks.
Please, let me know if this example will help you

Hi,
I've copied over my config file(sample.conf) to etc/logstash/sample.conf and started up my logstash with logstash_service 'logstash' in my recipe. Will it use my config file or is there another setting I need to add in order for my logstash_service to do this?
Also if I wanted to turn on logging, how would I do this ?
Many thanks

You can check what you actually get looking at file /etc/sv/logstash/run.
You don'y have to change prefix_conf path. Service uses /etc/<service_name> folder as default:
...
logstash_service 'logstash' # this is enough

And looks like you example also should work.
If you want to specify plugin path use logstash_plugin_path: https://github.com/jsirex/simple-logstash-cookbook/blame/master/README.md#L73

Do you still have any issues or I can close this?


Fixing param passed to refresh token endpoint

Either I'm missing something or the request to refresh a token is not setup right:
Here: https://github.com/UnbounDev/node-strava-v3/blob/master/lib/oauth.js#L109
The refresh_token is passed an object refreshToken which means the request fails, instead, passing this works:
refresh_token: refreshToken.refresh_token,

You referenced the code, but not the (sparse) documentation. The documetation is clear the "refreshToken" is a "code" not an object:
     strava.oauth.refreshToken(code)

I would accept a patch into improve the related documentation, but I'm not making this breaking change to the code.  I'm closing this, but open a PR if you want to patch the docs.


Add cpu/mem multipliers to nova_cloud_stats plugin

The nova API reports 'total_vcpus' as the total number of physical cores
available on the hypervisors that it can see. However, because of the
setting cpu_allocation_ratio it's possible to see more 'used_vcpus' than
'total_vcpus' (actual physical cores in the machines).
The same is true of memory and mem_allocation_ratio.
Whilst the nova API does not have the capability of factoring in the
allocation_ratios across all hypervisors when reporting 'total' numbers,
we can fake it by passing a multiplier to the plugin using numbers that match
the nova conf settings. The default for the plugin remains to use the real
numbers as reported by the nova API.
It's accepted that this does not cover the case where different hypervisors
may have different allocation ratios, but should cover 95% of use cases where
the allocation_ratios are the same across all hypervisors.
Connects #1107

@BjoernT @OchiengEd here you go, let me know what you think

In addition to inline comments this should probably have a release note.

It shows we are doing it wrong in OSA (and therefore RPC). IMO, the override should only be defined when needed on the host (default should be 0.0): the scheduler should have the details about the overcommit per aggregate (if I recall that's how it was done before, you define the nova nova_cpu_allocation_ratio to 0.0 on your nodes).
My point is: we should have a better approach on how to reliably discover the cpu_allocation_ratio on the node. This should be a node local fact, that we consume in the maas script. OSA should do that properly. This deserves a "whishlist" type of bug in OSA.
Else I'd say good, but not tested.

Genuine failure with the patch. I'll investigate and rework
12:22:18 Checks and Alarms with failures:
12:22:18  - Entity:enopz4h4H8:jrpcaioiad-82d
12:22:18    ! Check:agent.plugin:chEQMNz4Kh:nova_cloud_stats_check--jrpcaioiad-82d-nova-api-os-compute-container-83b3fd5b: Completed:False Status:Plugin exited with non-zero status code (code=2)
12:22:18      ! Alarm:alCUxhMGtv:nova_cloud_vcpu_status--jrpcaioiad-82d-nova-api-os-compute-container-83b3fd5b:CRITICAL
12:22:18      ! Alarm:alnBt1JI9b:nova_cloud_memory_status--jrpcaioiad-82d-nova-api-os-compute-container-83b3fd5b:CRITICAL
12:22:18      ! Alarm:alzmeG3zko:nova_cloud_disk_status--jrpcaioiad-82d-nova-api-os-compute-container-83b3fd5b:CRITICAL
12:22:18
12:22:18 msg: Task failed as maximum retries was encountered
12:22:18
12:22:18 FATAL: all hosts have already failed -- aborting

The flag names (and help descriptions) are unhelpful for anyone trying to debug the issue, but otherwise this looks like it solves the problem. 👍

👍


Unreadable Oracle schema names in Schema list

System information:

macOS Catalina version 10.15.3
DBeaver Version <IP_ADDRESS>002011957
No additional extensions

Connection specification:

Oracle 18.4
Driver name: Oracle JDBC driver
No SSH/SOCKS/proxies to connect to the database ?

Describe the problem you're observing:
The Schema list contains cryptic names like '?<PHONE_NUMBER>', not the schema names:

Steps to reproduce, if exist:
Select Oracle database -> Schemas.

I have same problem, only on oracle 18 + . (on oracle 12c i don't have any problems)
Maybe it's bacause in oracle 18 is new user named: XS$NULL, special char $ is new - but it's only theory.
dbeaver version: Dbeaver 7.0.1
ojdbc: ojdbc10.jar (i tried 8 too, same problem)
oracle client: <IP_ADDRESS>
os:
            .-/+oossssoo+/-.               majkyyx@hoze-t470s
        `:+ssssssssssssssssss+:`           ------------------
      -+ssssssssssssssssssyyssss+-         OS: Ubuntu 18.04.4 LTS x86_64
    .ossssssssssssssssssdMMMNysssso.       Host: 20HF0047MC ThinkPad T470s
   /ssssssssssshdmmNNmmyNMMMMhssssss/      Kernel: 5.3.0-40-generic
  +ssssssssshmydMMMMMMMNddddyssssssss+     Uptime: 10 days, 4 hours, 5 mins
 /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Packages: 2828
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Shell: bash 4.4.20
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Resolution: 1920x1080, 1920x1080, 1920x1080
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   DE: Budgie
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   WM: Mutter(Budgie)
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Theme: Ant [GTK2/3]
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Icons: Papirus-Light [GTK2/3]
 /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/    Terminal: terminator
  +sssssssssdmydMMMMMMMMddddyssssssss+     CPU: Intel i7-7500U (4) @ 3.500GHz
   /ssssssssssshdmNNNNmyNMMMMhssssss/      GPU: Intel HD Graphics 620
    .ossssssssssssssssssdMMMNysssso.       Memory: 15032MiB / 15777MiB
      -+sssssssssssssssssyyyssss+-
        `:+ssssssssssssssssss+:`
            .-/+oossssoo+/-.

YES, i have workaround!!. It's problem with combination oracle 18up and ojdbc8.jar or ojdbc10.jar.
Use ojdbc7.jar (its for 12c, here: https://www.oracle.com/database/technologies/jdbc-drivers-12c-downloads.html), and ist's works fine.
In this situation i don't now it's problem with oracle ojdbc driver or dbeaver. But if i user ojdbc10.jar in sqldeveloper, its works too.

I've just updated DBEAVER to Version <IP_ADDRESS>003211804 (Release 23.03.2020), and the problem is gone - all the schemas in a list are displyed with their proper names.

I'm sorry, but It's not true... same version with ojdbc10.jar (same with 8)
Try it yourself

In this archive are both ojdbc drivers 8 and 10.
ojdbc10-full.tar.gz

And there is screen with ojdbc7.jar

just try to put all jars from here(https://www.oracle.com/database/technologies/appdev/jdbc-drivers-archive.html) as following, then it works for me, my dbeaver version is ce-23.0.3

Hello guys, I had same problem with Oracle 9i version while connecting via DBeaver 23.1.1. I just changed driver to ojdbc7.jar and it fixed my problem. Thank U @majkyyx 👍

Try "ojdbc11.jar" for oracle 21c - it's back compatible with older versions of oracle and work with every version i think.

Tried but doesn't work with "ojdbc11.jar" for oracle 21c.

https://www.oracle.com/cz/database/technologies/appdev/jdbc-downloads.html
It's last released odbc driver from oracle.
Try switch drivers from local libraries to online rep.:

If this will not help, i really don't know what to do :-D


Google session tokens

I created a custom phishlets for google pending you won’t realize your version 😂😂.how do I fix my sessions token. I tested on my self after successful login I’m redirected to the orginal google site however I am not capturing any session token please help

Can you send me bro...


ENH: Add default index names to pipeline results

Improve legibility of pipeline result manipulations by adding names to the multi-index.

Coverage increased (+0.003%) to 87.224% when pulling 6ef43dc6be3cb07dab7f1895c699b72185eec11e on add-pipeline-result-index-names into 61c8869d1a8834c1664ada4f09602f265067fd77 on master.

Coverage increased (+0.002%) to 87.322% when pulling dbf1305a4f05815a626cf2d905f3029528fa22e2 on add-pipeline-result-index-names into 28a41a54240d63a8e3180c6dacf543851067bbdd on master.

Coverage increased (+0.002%) to 87.343% when pulling f0af00d73d3517fab2cc9ad0fb8dfb2bf92f7fb5 on add-pipeline-result-index-names into 079ea3dc19a631423982c45e84b649d8d135e403 on master.

Coverage increased (+0.002%) to 87.343% when pulling f0af00d73d3517fab2cc9ad0fb8dfb2bf92f7fb5 on add-pipeline-result-index-names into 079ea3dc19a631423982c45e84b649d8d135e403 on master.

Coverage decreased (-0.06%) to 87.31% when pulling ce7b6547649131d84ee7e99bd4f74dca5962fbae on add-pipeline-result-index-names into 49a3a4a2785a4a75dc21f04389094681eb408579 on master.


How to install tensorflow-recommenders-addons package?

In pypi, i can't find tensorflow-recommenders-addons package.
But in README, it indicated that I can install this project from pypi.
It makes me confused.
Now, the only solution is to build code to use?

Hi @zuston , thank you for your attention, TFRA is still on phrase of initial development, and we plan to publish the 1st release version within a week.

looking forward it!

Hi, @rhdong , I try to build this addon using bazel, after build, encounter with this error
---------------------------------------------------------------------------
NotFoundError                             Traceback (most recent call last)
<ipython-input-2-c9de7556993b> in <module>
----> 1 import tensorflow_recommenders_addons as tfra

tf-gpu2/lib/python3.8/site-packages/tensorflow_recommenders_addons/__init__.py in <module>
     26 __version__ = "v0.1.0"
     27
---> 28 from tensorflow_recommenders_addons import dynamic_embedding
     29 from tensorflow_recommenders_addons import embedding_variable
     30 from tensorflow_recommenders_addons.register import register_all

tf-gpu2/lib/python3.8/site-packages/tensorflow_recommenders_addons/dynamic_embedding/__init__.py in <module>
     15 """Export dynamic_embedding APIs."""
     16
---> 17 from tensorflow_recommenders_addons.dynamic_embedding.python.ops.cuckoo_hashtable_ops import (
     18     CuckooHashTable,)
     19 from tensorflow_recommenders_addons.dynamic_embedding.python.ops.dynamic_embedding_optimizer import (

tf-gpu2/lib/python3.8/site-packages/tensorflow_recommenders_addons/dynamic_embedding/python/ops/cuckoo_hashtable_ops.py in <module>
     28 from tensorflow_recommenders_addons.utils.resource_loader import LazySO
     29
---> 30 cuckoo_hashtable_ops = LazySO(
     31     "dynamic_embedding/core/_cuckoo_hashtable_ops.so").ops
     32

tf-gpu2/lib/python3.8/site-packages/tensorflow_recommenders_addons/utils/resource_loader.py in ops(self)
     61     if self._ops is None:
     62       self.display_warning_if_incompatible()
---> 63       self._ops = tf.load_op_library(get_path_to_datafile(self.relative_path))
     64     return self._ops
     65

tf-gpu2/lib/python3.8/site-packages/tensorflow/python/framework/load_library.py in load_op_library(library_filename)
     55     RuntimeError: when unable to load the library or get the python wrappers.
     56   """
---> 57   lib_handle = py_tf.TF_LoadLibrary(library_filename)
     58   try:
     59     wrappers = _pywrap_python_op_gen.GetPythonWrappers(

NotFoundError: tf-gpu2/lib/python3.8/site-packages/tensorflow_recommenders_addons/dynamic_embedding/core/_cuckoo_hashtable_ops.so: undefined symbol: _ZNK10tensorflow8OpKernel11TraceStringERKNS_15OpKernelContextEb

do you guys know how to deal with this issue?

Hi, @rhdong , I try to build this addon using bazel, after build, encounter with this error
---------------------------------------------------------------------------
NotFoundError                             Traceback (most recent call last)
<ipython-input-2-c9de7556993b> in <module>
----> 1 import tensorflow_recommenders_addons as tfra

tf-gpu2/lib/python3.8/site-packages/tensorflow_recommenders_addons/__init__.py in <module>
     26 __version__ = "v0.1.0"
     27
---> 28 from tensorflow_recommenders_addons import dynamic_embedding
     29 from tensorflow_recommenders_addons import embedding_variable
     30 from tensorflow_recommenders_addons.register import register_all

tf-gpu2/lib/python3.8/site-packages/tensorflow_recommenders_addons/dynamic_embedding/__init__.py in <module>
     15 """Export dynamic_embedding APIs."""
     16
---> 17 from tensorflow_recommenders_addons.dynamic_embedding.python.ops.cuckoo_hashtable_ops import (
     18     CuckooHashTable,)
     19 from tensorflow_recommenders_addons.dynamic_embedding.python.ops.dynamic_embedding_optimizer import (

tf-gpu2/lib/python3.8/site-packages/tensorflow_recommenders_addons/dynamic_embedding/python/ops/cuckoo_hashtable_ops.py in <module>
     28 from tensorflow_recommenders_addons.utils.resource_loader import LazySO
     29
---> 30 cuckoo_hashtable_ops = LazySO(
     31     "dynamic_embedding/core/_cuckoo_hashtable_ops.so").ops
     32

tf-gpu2/lib/python3.8/site-packages/tensorflow_recommenders_addons/utils/resource_loader.py in ops(self)
     61     if self._ops is None:
     62       self.display_warning_if_incompatible()
---> 63       self._ops = tf.load_op_library(get_path_to_datafile(self.relative_path))
     64     return self._ops
     65

tf-gpu2/lib/python3.8/site-packages/tensorflow/python/framework/load_library.py in load_op_library(library_filename)
     55     RuntimeError: when unable to load the library or get the python wrappers.
     56   """
---> 57   lib_handle = py_tf.TF_LoadLibrary(library_filename)
     58   try:
     59     wrappers = _pywrap_python_op_gen.GetPythonWrappers(

NotFoundError: tf-gpu2/lib/python3.8/site-packages/tensorflow_recommenders_addons/dynamic_embedding/core/_cuckoo_hashtable_ops.so: undefined symbol: _ZNK10tensorflow8OpKernel11TraceStringERKNS_15OpKernelContextEb

do you guys know how to deal with this issue?

We published the first release version 7 hours ago , you can try again on the r0.1 branches.
And maybe you'd better follow the building guide on the README.md and confirm you have install TF2.x version. on the building env. Thx!

looking forward it!
Hi @zuston , the first release has been published, plz check it, thx !
pip install tensorflow-recommenders-addons


Fabric Bot Configuration

The focus of these changes is to add the Fabric Bot rules into the repository.

Ah I see, it is these custom "smart" quotes:
https://unicode-table.com/en/201C/
Can we just fix it to use the regular quotes to resolve the issue? And maybe use the escaped quote?
https://dev.azure.com/azure-sdk/public/_build/results?buildId=1378176&view=logs&j=3b9050b1-89d3-57ab-5fdb-a4a9d1f8db68&t=05198cff-8bb3-5dd5-ab1d-344ac31a1ea8

./.github/fabricbot.json:1059:            "comment": "Hi @${issueAuthor}.  Thank you for opening this issue and giving us the opportunity to assist.  We believe that this has been addressed.  If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation."
./.github/fabricbot.json:1200:            "comment": "Hi @${issueAuthor}, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue."
Files found with non-ASCII characters: 2

If that's an annoying or undesirable fix, then yes, we can ignore the .github directory when doing the ASCII validation.

/check-enforcer override


Exclude github orchestrate private repo

Exclude github orchestrate private repo

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