Reg:Couldn't determine robot's pose associated with laser scan - burger

Hi
I am getting the error while I am doing navigation topic in turtlebot3 burger using ROS Kinetic on Ubuntu 16.04
[ERROR] [1571763280.542860289]: Couldn't determine robot's pose associated with laser scan
Help me to solve this error? (More specifically while running amcl.launch)
But while doing slam.launch , it is working.

@tatag4u
Hi,
Thank you for your inquiry.
While I'm awaiting from developers reply, could you please share us more detailed information?
For example, in which procedure you run the commands and what kind of error messages did you get from each terminal?
Thank you.

Hi,
Thanks for your reply.
First I have created map using SLAM and it is stored in $HOME/map.yaml
1)Remote PC: $ roscore
... logging to /home/shiva/.ros/log/4962bb22-0242-11ea-a2c4-8cec4b6feb32/roslaunch-shiva-8415.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://<IP_ADDRESS>:36839/
ros_comm version 1.12.14
SUMMARY
PARAMETERS

/rosdistro: kinetic
/rosversion: 1.12.14

NODES
auto-starting new master
process[master]: started with pid [8425]
ROS_MASTER_URI=http://<IP_ADDRESS>:11311/
setting /run_id to 4962bb22-0242-11ea-a2c4-8cec4b6feb32
process[rosout-1]: started with pid [8438]
started core service [/rosout]
2)Turtlebot3 (burger):$ roslaunch turtlebot3_bringup turtlebot3_robot.launch
... logging to /home/pi/.ros/log/4962bb22-0242-11ea-a2c4-8cec4b6feb32/roslaunch-raspberrypi-1094.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://<IP_ADDRESS>:42211/
SUMMARY
PARAMETERS

/rosdistro: kinetic
/rosversion: 1.12.13
/turtlebot3_core/baud: 115200
/turtlebot3_core/port: /dev/ttyACM0
/turtlebot3_core/tf_prefix:
/turtlebot3_lds/frame_id: odom
/turtlebot3_lds/port: /dev/ttyUSB0

NODES
/
turtlebot3_core (rosserial_python/serial_node.py)
turtlebot3_diagnostics (turtlebot3_bringup/turtlebot3_diagnostics)
turtlebot3_lds (hls_lfcd_lds_driver/hlds_laser_publisher)
ROS_MASTER_URI=http://<IP_ADDRESS>:11311
process[turtlebot3_core-1]: started with pid [1120]
process[turtlebot3_lds-2]: started with pid [1121]
process[turtlebot3_diagnostics-3]: started with pid [1122]
[INFO] [1572526178.943060]: ROS Serial Python Node
[INFO] [1572526178.974476]: Connecting to /dev/ttyACM0 at 115200 baud
[INFO] [1572526181.121154]: Note: publish buffer size is 1024 bytes
[INFO] [1572526181.124335]: Setup publisher on sensor_state [turtlebot3_msgs/SensorState]
[INFO] [1572526181.140936]: Setup publisher on firmware_version [turtlebot3_msgs/VersionInfo]
[INFO] [1572526181.297942]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1572526181.308419]: Setup publisher on cmd_vel_rc100 [geometry_msgs/Twist]
[INFO] [1572526181.356831]: Setup publisher on odom [nav_msgs/Odometry]
[INFO] [1572526181.367697]: Setup publisher on joint_states [sensor_msgs/JointState]
[INFO] [1572526181.378821]: Setup publisher on battery_state [sensor_msgs/BatteryState]
[INFO] [1572526181.390517]: Setup publisher on magnetic_field [sensor_msgs/MagneticField]
[INFO] [1572526184.497769]: Setup publisher on /tf [tf/tfMessage]
[INFO] [1572526184.514315]: Note: subscribe buffer size is 1024 bytes
[INFO] [1572526184.515781]: Setup subscriber on cmd_vel [geometry_msgs/Twist]
[INFO] [1572526184.531675]: Setup subscriber on sound [turtlebot3_msgs/Sound]
[INFO] [1572526184.551571]: Setup subscriber on motor_power [std_msgs/Bool]
[INFO] [1572526184.570389]: Setup subscriber on reset [std_msgs/Empty]
[INFO] [1572526184.584121]: Setup TF on Odometry [odom]
[INFO] [1572526184.587735]: Setup TF on IMU [imu_link]
[INFO] [1572526184.591144]: Setup TF on MagneticField [mag_link]
[INFO] [1572526184.594693]: Setup TF on JointState [base_link]
[INFO] [1572526184.602656]: --------------------------
[INFO] [1572526184.606141]: Connected to OpenCR board!
[INFO] [1572526184.609488]: This core(v1.2.3) is compatible with TB3 Burger
[INFO] [1572526184.612999]: --------------------------
[INFO] [1572526184.616464]: Start Calibration of Gyro
[INFO] [1572526187.146208]: Calibration End
3)Remote PC:
$ export TURTLEBOT3_MODEL=burger
$ roslaunch turtlebot3_navigation turtlebot3_navigation.launch map_file:=$HOME/map.yaml
... logging to /home/shiva/.ros/log/4962bb22-0242-11ea-a2c4-8cec4b6feb32/roslaunch-shiva-8862.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/loader.py:409: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
data = yaml.load(text)
started roslaunch server http://<IP_ADDRESS>:38877/
SUMMARY
PARAMETERS

/amcl/base_frame_id: base_footprint
/amcl/gui_publish_rate: 50.0
/amcl/initial_pose_a: 0.0
/amcl/initial_pose_x: 0.0
/amcl/initial_pose_y: 0.0
/amcl/kld_err: 0.02
/amcl/laser_lambda_short: 0.1
/amcl/laser_likelihood_max_dist: 2.0
/amcl/laser_max_beams: 180
/amcl/laser_max_range: 3.5
/amcl/laser_model_type: likelihood_field
/amcl/laser_sigma_hit: 0.2
/amcl/laser_z_hit: 0.5
/amcl/laser_z_max: 0.05
/amcl/laser_z_rand: 0.5
/amcl/laser_z_short: 0.05
/amcl/max_particles: 3000
/amcl/min_particles: 500
/amcl/odom_alpha1: 0.1
/amcl/odom_alpha2: 0.1
/amcl/odom_alpha3: 0.1
/amcl/odom_alpha4: 0.1
/amcl/odom_frame_id: odom
/amcl/odom_model_type: diff
/amcl/recovery_alpha_fast: 0.0
/amcl/recovery_alpha_slow: 0.0
/amcl/resample_interval: 1
/amcl/transform_tolerance: 0.5
/amcl/update_min_a: 0.2
/amcl/update_min_d: 0.2
/move_base/DWAPlannerROS/acc_lim_theta: 3.2
/move_base/DWAPlannerROS/acc_lim_x: 2.5
/move_base/DWAPlannerROS/acc_lim_y: 0.0
/move_base/DWAPlannerROS/controller_frequency: 10.0
/move_base/DWAPlannerROS/forward_point_distance: 0.325
/move_base/DWAPlannerROS/goal_distance_bias: 20.0
/move_base/DWAPlannerROS/latch_xy_goal_tolerance: False
/move_base/DWAPlannerROS/max_rot_vel: 2.75
/move_base/DWAPlannerROS/max_scaling_factor: 0.2
/move_base/DWAPlannerROS/max_trans_vel: 0.22
/move_base/DWAPlannerROS/max_vel_x: 0.22
/move_base/DWAPlannerROS/max_vel_y: 0.0
/move_base/DWAPlannerROS/min_rot_vel: 1.37
/move_base/DWAPlannerROS/min_trans_vel: 0.11
/move_base/DWAPlannerROS/min_vel_x: -0.22
/move_base/DWAPlannerROS/min_vel_y: 0.0
/move_base/DWAPlannerROS/occdist_scale: 0.02
/move_base/DWAPlannerROS/oscillation_reset_dist: 0.05
/move_base/DWAPlannerROS/path_distance_bias: 32.0
/move_base/DWAPlannerROS/publish_cost_grid_pc: True
/move_base/DWAPlannerROS/publish_traj_pc: True
/move_base/DWAPlannerROS/scaling_speed: 0.25
/move_base/DWAPlannerROS/sim_time: 1.5
/move_base/DWAPlannerROS/stop_time_buffer: 0.2
/move_base/DWAPlannerROS/vth_samples: 40
/move_base/DWAPlannerROS/vx_samples: 20
/move_base/DWAPlannerROS/vy_samples: 0
/move_base/DWAPlannerROS/xy_goal_tolerance: 0.05
/move_base/DWAPlannerROS/yaw_goal_tolerance: 0.17
/move_base/base_local_planner: dwa_local_planner...
/move_base/conservative_reset_dist: 3.0
/move_base/controller_frequency: 10.0
/move_base/controller_patience: 15.0
/move_base/global_costmap/cost_scaling_factor: 3.0
/move_base/global_costmap/footprint: [[-0.105, -0.105]...
/move_base/global_costmap/global_frame: map
/move_base/global_costmap/inflation_radius: 1.0
/move_base/global_costmap/map_type: costmap
/move_base/global_costmap/observation_sources: scan
/move_base/global_costmap/obstacle_range: 3.0
/move_base/global_costmap/publish_frequency: 10.0
/move_base/global_costmap/raytrace_range: 3.5
/move_base/global_costmap/robot_base_frame: base_footprint
/move_base/global_costmap/scan/clearing: True
/move_base/global_costmap/scan/data_type: LaserScan
/move_base/global_costmap/scan/marking: True
/move_base/global_costmap/scan/sensor_frame: base_scan
/move_base/global_costmap/scan/topic: scan
/move_base/global_costmap/static_map: True
/move_base/global_costmap/transform_tolerance: 0.5
/move_base/global_costmap/update_frequency: 10.0
/move_base/local_costmap/cost_scaling_factor: 3.0
/move_base/local_costmap/footprint: [[-0.105, -0.105]...
/move_base/local_costmap/global_frame: odom
/move_base/local_costmap/height: 3
/move_base/local_costmap/inflation_radius: 1.0
/move_base/local_costmap/map_type: costmap
/move_base/local_costmap/observation_sources: scan
/move_base/local_costmap/obstacle_range: 3.0
/move_base/local_costmap/publish_frequency: 10.0
/move_base/local_costmap/raytrace_range: 3.5
/move_base/local_costmap/resolution: 0.05
/move_base/local_costmap/robot_base_frame: base_footprint
/move_base/local_costmap/rolling_window: True
/move_base/local_costmap/scan/clearing: True
/move_base/local_costmap/scan/data_type: LaserScan
/move_base/local_costmap/scan/marking: True
/move_base/local_costmap/scan/sensor_frame: base_scan
/move_base/local_costmap/scan/topic: scan
/move_base/local_costmap/static_map: False
/move_base/local_costmap/transform_tolerance: 0.5
/move_base/local_costmap/update_frequency: 10.0
/move_base/local_costmap/width: 3
/move_base/oscillation_distance: 0.2
/move_base/oscillation_timeout: 10.0
/move_base/planner_frequency: 5.0
/move_base/planner_patience: 5.0
/move_base/shutdown_costmaps: False
/robot_description: <?xml version="1....
/robot_state_publisher/publish_frequency: 50.0
/robot_state_publisher/tf_prefix:
/rosdistro: kinetic
/rosversion: 1.12.14

NODES
/
amcl (amcl/amcl)
map_server (map_server/map_server)
move_base (move_base/move_base)
robot_state_publisher (robot_state_publisher/robot_state_publisher)
rviz (rviz/rviz)
ROS_MASTER_URI=http://<IP_ADDRESS>:11311
process[robot_state_publisher-1]: started with pid [8882]
process[map_server-2]: started with pid [8883]
process[amcl-3]: started with pid [8884]
process[move_base-4]: started with pid [8885]
process[rviz-5]: started with pid [8926]
[ERROR] [1573229871.024452125]: Couldn't determine robot's pose associated with laser scan
[ERROR] [1573229871.223923323]: Couldn't determine robot's pose associated with laser scan
[ERROR] [1573229871.424800239]: Couldn't determine robot's pose associated with laser scan
[ERROR] [1573229871.624859740]: Couldn't determine robot's pose associated with laser scan
[ERROR] [1573229871.825876669]: Couldn't determine robot's pose associated with laser scan
[ERROR] [1573229872.027099129]: Couldn't determine robot's pose associated with laser scan
[ERROR] [1573229872.226931119]: Couldn't determine robot's pose associated with laser scan
[ERROR] [1573229872.428440502]: Couldn't determine robot's pose associated with laser scan
[ERROR] [1573229873.030265817]: Couldn't determine robot's pose associated with laser scan
[ INFO] [1573229873.142097091]: Loading from pre-hydro parameter style
[ INFO] [1573229873.166692137]: Using plugin "static_layer"
[ERROR] [1573229873.231576356]: Couldn't determine robot's pose associated with laser scan
[ INFO] [1573229873.313660727]: Requesting the map...
[ERROR] [1573229873.431566547]: Couldn't determine robot's pose associated with laser scan
[ INFO] [1573229873.525439951]: Resizing costmap to 384 X 384 at 0.050000 m/pix
[ INFO] [1573229873.625207995]: Received a 384 X 384 map at 0.050000 m/pix
[ERROR] [1573229873.632271074]: Couldn't determine robot's pose associated with laser scan
[ INFO] [1573229873.635647556]: Using plugin "obstacle_layer"
[ INFO] [1573229873.641262863]:     Subscribed to Topics: scan
[ INFO] [1573229873.705044711]: Using plugin "inflation_layer"
[ WARN] [1573229873.775901568]: Costmap2DROS transform timeout. Current time:<PHONE_NUMBER>.7757, global_pose stamp:<PHONE_NUMBER>.3082, tolerance: 0.5000
[ INFO] [1573229873.824769980]: Loading from pre-hydro parameter style
[ERROR] [1573229873.832147684]: Couldn't determine robot's pose associated with laser scan
[ INFO] [1573229873.877711506]: Using plugin "obstacle_layer"
[ INFO] [1573229873.880744097]:     Subscribed to Topics: scan
[ INFO] [1573229873.911904576]: Using plugin "inflation_layer"
[ INFO] [1573229873.987216365]: Created local_planner dwa_local_planner/DWAPlannerROS
[ INFO] [1573229873.994790930]: Sim period is set to 0.10
[ERROR] [1573229874.034628161]: Couldn't determine robot's pose associated with laser scan
[ERROR] [1573229874.234476554]: Couldn't determine robot's pose associated with laser scan
[ERROR] [1573229874.435480491]: Couldn't determine robot's pose associated with laser scan
[ERROR] [1573229874.635490807]: Couldn't determine robot's pose associated with laser scan
[ERROR] [1573229874.837085706]: Couldn't determine robot's pose associated with laser scan
[ WARN] [1573229874.875884254]: Costmap2DROS transform timeout.  Current time:<PHONE_NUMBER>.8758, global_pose stamp:<PHONE_NUMBER>.3082, tolerance: 0.5000
,, ,,  ,,, .................
The error is repeated again.....
I run this on ROS on Ubuntu 16.04.

Hi,
Thanks for your reply.
First I have created map using SLAM (map is stored in $HOME/map.yaml)
1)Remote PC: $ roscore
... logging to
/home/shiva/.ros/log/4962bb22-0242-11ea-a2c4-8cec4b6feb32/roslaunch-shiva-8415.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://<IP_ADDRESS>:36839/
ros_comm version 1.12.14
SUMMARY
PARAMETERS

/rosdistro: kinetic
/rosversion: 1.12.14

NODES
auto-starting new master
process[master]: started with pid [8425]
ROS_MASTER_URI=http://<IP_ADDRESS>:11311/
setting /run_id to 4962bb22-0242-11ea-a2c4-8cec4b6feb32
process[rosout-1]: started with pid [8438]
started core service [/rosout]
2)Turtlebot3 (burger):$ roslaunch turtlebot3_bringup
turtlebot3_robot.launch
... logging to
/home/pi/.ros/log/4962bb22-0242-11ea-a2c4-8cec4b6feb32/roslaunch-raspberrypi-1094.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://<IP_ADDRESS>:42211/
SUMMARY
PARAMETERS

/rosdistro: kinetic
/rosversion: 1.12.13
/turtlebot3_core/baud: 115200
/turtlebot3_core/port: /dev/ttyACM0
/turtlebot3_core/tf_prefix:
/turtlebot3_lds/frame_id: odom
/turtlebot3_lds/port: /dev/ttyUSB0

NODES
/
turtlebot3_core (rosserial_python/serial_node.py)
turtlebot3_diagnostics (turtlebot3_bringup/turtlebot3_diagnostics)
turtlebot3_lds (hls_lfcd_lds_driver/hlds_laser_publisher)
ROS_MASTER_URI=http://<IP_ADDRESS>:11311
process[turtlebot3_core-1]: started with pid [1120]
process[turtlebot3_lds-2]: started with pid [1121]
process[turtlebot3_diagnostics-3]: started with pid [1122]
[INFO] [1572526178.943060]: ROS Serial Python Node
[INFO] [1572526178.974476]: Connecting to /dev/ttyACM0 at 115200 baud
[INFO] [1572526181.121154]: Note: publish buffer size is 1024 bytes
[INFO] [1572526181.124335]: Setup publisher on sensor_state
[turtlebot3_msgs/SensorState]
[INFO] [1572526181.140936]: Setup publisher on firmware_version
[turtlebot3_msgs/VersionInfo]
[INFO] [1572526181.297942]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1572526181.308419]: Setup publisher on cmd_vel_rc100
[geometry_msgs/Twist]
[INFO] [1572526181.356831]: Setup publisher on odom [nav_msgs/Odometry]
[INFO] [1572526181.367697]: Setup publisher on joint_states
[sensor_msgs/JointState]
[INFO] [1572526181.378821]: Setup publisher on battery_state
[sensor_msgs/BatteryState]
[INFO] [1572526181.390517]: Setup publisher on magnetic_field
[sensor_msgs/MagneticField]
[INFO] [1572526184.497769]: Setup publisher on /tf [tf/tfMessage]
[INFO] [1572526184.514315]: Note: subscribe buffer size is 1024 bytes
[INFO] [1572526184.515781]: Setup subscriber on cmd_vel
[geometry_msgs/Twist]
[INFO] [1572526184.531675]: Setup subscriber on sound
[turtlebot3_msgs/Sound]
[INFO] [1572526184.551571]: Setup subscriber on motor_power [std_msgs/Bool]
[INFO] [1572526184.570389]: Setup subscriber on reset [std_msgs/Empty]
[INFO] [1572526184.584121]: Setup TF on Odometry [odom]
[INFO] [1572526184.587735]: Setup TF on IMU [imu_link]
[INFO] [1572526184.591144]: Setup TF on MagneticField [mag_link]
[INFO] [1572526184.594693]: Setup TF on JointState [base_link]
[INFO] [1572526184.602656]: --------------------------
[INFO] [1572526184.606141]: Connected to OpenCR board!
[INFO] [1572526184.609488]: This core(v1.2.3) is compatible with TB3 Burger
[INFO] [1572526184.612999]: --------------------------
[INFO] [1572526184.616464]: Start Calibration of Gyro
[INFO] [1572526187.146208]: Calibration End
3)Remote PC: $ export TURTLEBOT3_MODEL=burger $ roslaunch
turtlebot3_navigation turtlebot3_navigation.launch map_file:=$HOME/map.yaml
... logging to
/home/shiva/.ros/log/4962bb22-0242-11ea-a2c4-8cec4b6feb32/roslaunch-shiva-8862.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/loader.py:409:
YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as
the default Loader is unsafe. Please read https://msg.pyyaml.org/load for
full details.
data = yaml.load(text)
started roslaunch server http://<IP_ADDRESS>:38877/
SUMMARY
PARAMETERS

/amcl/base_frame_id: base_footprint
/amcl/gui_publish_rate: 50.0
/amcl/initial_pose_a: 0.0
/amcl/initial_pose_x: 0.0
/amcl/initial_pose_y: 0.0
/amcl/kld_err: 0.02
/amcl/laser_lambda_short: 0.1
/amcl/laser_likelihood_max_dist: 2.0
/amcl/laser_max_beams: 180
/amcl/laser_max_range: 3.5
/amcl/laser_model_type: likelihood_field
/amcl/laser_sigma_hit: 0.2
/amcl/laser_z_hit: 0.5
/amcl/laser_z_max: 0.05
/amcl/laser_z_rand: 0.5
/amcl/laser_z_short: 0.05
/amcl/max_particles: 3000
/amcl/min_particles: 500
/amcl/odom_alpha1: 0.1
/amcl/odom_alpha2: 0.1
/amcl/odom_alpha3: 0.1
/amcl/odom_alpha4: 0.1
/amcl/odom_frame_id: odom
/amcl/odom_model_type: diff
/amcl/recovery_alpha_fast: 0.0
/amcl/recovery_alpha_slow: 0.0
/amcl/resample_interval: 1
/amcl/transform_tolerance: 0.5
/amcl/update_min_a: 0.2
/amcl/update_min_d: 0.2
/move_base/DWAPlannerROS/acc_lim_theta: 3.2
/move_base/DWAPlannerROS/acc_lim_x: 2.5
/move_base/DWAPlannerROS/acc_lim_y: 0.0
/move_base/DWAPlannerROS/controller_frequency: 10.0
/move_base/DWAPlannerROS/forward_point_distance: 0.325
/move_base/DWAPlannerROS/goal_distance_bias: 20.0
/move_base/DWAPlannerROS/latch_xy_goal_tolerance: False
/move_base/DWAPlannerROS/max_rot_vel: 2.75
/move_base/DWAPlannerROS/max_scaling_factor: 0.2
/move_base/DWAPlannerROS/max_trans_vel: 0.22
/move_base/DWAPlannerROS/max_vel_x: 0.22
/move_base/DWAPlannerROS/max_vel_y: 0.0
/move_base/DWAPlannerROS/min_rot_vel: 1.37
/move_base/DWAPlannerROS/min_trans_vel: 0.11
/move_base/DWAPlannerROS/min_vel_x: -0.22
/move_base/DWAPlannerROS/min_vel_y: 0.0
/move_base/DWAPlannerROS/occdist_scale: 0.02
/move_base/DWAPlannerROS/oscillation_reset_dist: 0.05
/move_base/DWAPlannerROS/path_distance_bias: 32.0
/move_base/DWAPlannerROS/publish_cost_grid_pc: True
/move_base/DWAPlannerROS/publish_traj_pc: True
/move_base/DWAPlannerROS/scaling_speed: 0.25
/move_base/DWAPlannerROS/sim_time: 1.5
/move_base/DWAPlannerROS/stop_time_buffer: 0.2
/move_base/DWAPlannerROS/vth_samples: 40
/move_base/DWAPlannerROS/vx_samples: 20
/move_base/DWAPlannerROS/vy_samples: 0
/move_base/DWAPlannerROS/xy_goal_tolerance: 0.05
/move_base/DWAPlannerROS/yaw_goal_tolerance: 0.17
/move_base/base_local_planner: dwa_local_planner...
/move_base/conservative_reset_dist: 3.0
/move_base/controller_frequency: 10.0
/move_base/controller_patience: 15.0
/move_base/global_costmap/cost_scaling_factor: 3.0
/move_base/global_costmap/footprint: [[-0.105, -0.105]...
/move_base/global_costmap/global_frame: map
/move_base/global_costmap/inflation_radius: 1.0
/move_base/global_costmap/map_type: costmap
/move_base/global_costmap/observation_sources: scan
/move_base/global_costmap/obstacle_range: 3.0
/move_base/global_costmap/publish_frequency: 10.0
/move_base/global_costmap/raytrace_range: 3.5
/move_base/global_costmap/robot_base_frame: base_footprint
/move_base/global_costmap/scan/clearing: True
/move_base/global_costmap/scan/data_type: LaserScan
/move_base/global_costmap/scan/marking: True
/move_base/global_costmap/scan/sensor_frame: base_scan
/move_base/global_costmap/scan/topic: scan
/move_base/global_costmap/static_map: True
/move_base/global_costmap/transform_tolerance: 0.5
/move_base/global_costmap/update_frequency: 10.0
/move_base/local_costmap/cost_scaling_factor: 3.0
/move_base/local_costmap/footprint: [[-0.105, -0.105]...
/move_base/local_costmap/global_frame: odom
/move_base/local_costmap/height: 3
/move_base/local_costmap/inflation_radius: 1.0
/move_base/local_costmap/map_type: costmap
/move_base/local_costmap/observation_sources: scan
/move_base/local_costmap/obstacle_range: 3.0
/move_base/local_costmap/publish_frequency: 10.0
/move_base/local_costmap/raytrace_range: 3.5
/move_base/local_costmap/resolution: 0.05
/move_base/local_costmap/robot_base_frame: base_footprint
/move_base/local_costmap/rolling_window: True
/move_base/local_costmap/scan/clearing: True
/move_base/local_costmap/scan/data_type: LaserScan
/move_base/local_costmap/scan/marking: True
/move_base/local_costmap/scan/sensor_frame: base_scan
/move_base/local_costmap/scan/topic: scan
/move_base/local_costmap/static_map: False
/move_base/local_costmap/transform_tolerance: 0.5
/move_base/local_costmap/update_frequency: 10.0
/move_base/local_costmap/width: 3
/move_base/oscillation_distance: 0.2
/move_base/oscillation_timeout: 10.0
/move_base/planner_frequency: 5.0
/move_base/planner_patience: 5.0
/move_base/shutdown_costmaps: False
/robot_description: <?xml version="1....
/robot_state_publisher/publish_frequency: 50.0
/robot_state_publisher/tf_prefix:
/rosdistro: kinetic
/rosversion: 1.12.14

NODES
/
amcl (amcl/amcl)
map_server (map_server/map_server)
move_base (move_base/move_base)
robot_state_publisher (robot_state_publisher/robot_state_publisher)
rviz (rviz/rviz)
ROS_MASTER_URI=http://<IP_ADDRESS>:11311
process[robot_state_publisher-1]: started with pid [8882]
process[map_server-2]: started with pid [8883]
process[amcl-3]: started with pid [8884]
process[move_base-4]: started with pid [8885]
process[rviz-5]: started with pid [8926]
[ERROR] [1573229871.024452125]: Couldn't determine robot's pose associated
with laser scan [ERROR] [1573229871.223923323]: Couldn't determine robot's
pose associated with laser scan [ERROR] [1573229871.424800239]: Couldn't
determine robot's pose associated with laser scan [ERROR]
[1573229871.624859740]: Couldn't determine robot's pose associated with
laser scan [ERROR] [1573229871.825876669]: Couldn't determine robot's pose
associated with laser scan [ERROR] [1573229872.027099129]: Couldn't
determine robot's pose associated with laser scan [ERROR]
[1573229872.226931119]: Couldn't determine robot's pose associated with
laser scan [ERROR] [1573229872.428440502]: Couldn't determine robot's pose
associated with laser scan [ERROR] [1573229873.030265817]: Couldn't
determine robot's pose associated with laser scan
[ INFO] [1573229873.142097091]: Loading from pre-hydro parameter style
[ INFO] [1573229873.166692137]: Using plugin "static_layer"
[ERROR] [1573229873.231576356]: Couldn't determine robot's pose associated
with laser scan
[ INFO] [1573229873.313660727]: Requesting the map...
[ERROR] [1573229873.431566547]: Couldn't determine robot's pose associated
with laser scan
[ INFO] [1573229873.525439951]: Resizing costmap to 384 X 384 at 0.050000
m/pix
[ INFO] [1573229873.625207995]: Received a 384 X 384 map at 0.050000 m/pix
[ERROR] [1573229873.632271074]: Couldn't determine robot's pose associated
with laser scan
[ INFO] [1573229873.635647556]: Using plugin "obstacle_layer"
[ INFO] [1573229873.641262863]: Subscribed to Topics: scan
[ INFO] [1573229873.705044711]: Using plugin "inflation_layer"
[ WARN] [1573229873.775901568]: Costmap2DROS transform timeout. Current
time:<PHONE_NUMBER>.7757, global_pose stamp:<PHONE_NUMBER>.3082, tolerance: 0.5000
[ INFO] [1573229873.824769980]: Loading from pre-hydro parameter style
[ERROR] [1573229873.832147684]: Couldn't determine robot's pose associated
with laser scan
[ INFO] [1573229873.877711506]: Using plugin "obstacle_layer"
[ INFO] [1573229873.880744097]: Subscribed to Topics: scan
[ INFO] [1573229873.911904576]: Using plugin "inflation_layer"
[ INFO] [1573229873.987216365]: Created local_planner
dwa_local_planner/DWAPlannerROS
[ INFO] [1573229873.994790930]: Sim period is set to 0.10
[ERROR] [1573229874.034628161]: Couldn't determine robot's pose associated
with laser scan [ERROR] [1573229874.234476554]: Couldn't determine robot's
pose associated with laser scan [ERROR] [1573229874.435480491]: Couldn't
determine robot's pose associated with laser scan [ERROR]
[1573229874.635490807]: Couldn't determine robot's pose associated with
laser scan [ERROR] [1573229874.837085706]: Couldn't determine robot's pose
associated with laser scan [ WARN] [1573229874.875884254]: Costmap2DROS
transform timeout.
Current time:<PHONE_NUMBER>.8758, global_pose stamp:<PHONE_NUMBER>.3082,
tolerance: 0.5000
,, ,, ,,, .................
The error is repeated again.....
I run this on ROS on Ubuntu 16.04.
Thank you
Siva
On Thu, Nov 7, 2019 at 12:53 PM Will Son<EMAIL_ADDRESS>wrote:

@tatag4u https://github.com/tatag4u
Hi,
Thank you for your inquiry.
While I'm awaiting from developers reply, could you please share us more
detailed information?
For example, in which procedure you run the commands and what kind of
error messages did you get from each terminal?
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ROBOTIS-GIT/turtlebot3/issues/505?email_source=notifications&email_token=AGAXNYEA4HN543JJ6NND2I3QSO66JA5CNFSM4JDOI6XKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDLO7VA#issuecomment-550957012,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGAXNYG5WYCVMD3VO677XODQSO66JANCNFSM4JDOI6XA
.

--
[image: animated-india-flag-image-0004]
With Regards
G.Sivasankar
Assistant Professor(Sr)
Department of ECE
Mepco Schlenk Engineering College, Sivakasi-626005
Ph.+91-4562-235429,09791562538

Hi
I have attached rqt_graph.
Thank you
Siva
On Thu, Nov 7, 2019 at 12:53 PM Will Son<EMAIL_ADDRESS>wrote:

@tatag4u https://github.com/tatag4u
Hi,
Thank you for your inquiry.
While I'm awaiting from developers reply, could you please share us more
detailed information?
For example, in which procedure you run the commands and what kind of
error messages did you get from each terminal?
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ROBOTIS-GIT/turtlebot3/issues/505?email_source=notifications&email_token=AGAXNYEA4HN543JJ6NND2I3QSO66JA5CNFSM4JDOI6XKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDLO7VA#issuecomment-550957012,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGAXNYG5WYCVMD3VO677XODQSO66JANCNFSM4JDOI6XA
.

@tatag4u
Hi,
Thank you for attaching the log.
Have you performed Initial Pose estimation written on eManual?
http://emanual.robotis.com/docs/en/platform/turtlebot3/navigation/#estimate-initial-pose
After map and TurtleBot3 is loaded on the RViz screen, there's a 2D Pose Estimate button on top so that you can locate the initial pose of the actual robot in the map.
This has to be done before running the navigation.
Thank you.

Hi
I have done 2D Pose estimate, but not exactly match with map(very small
offset is present between given map to lidar data).
With Regards
G.Sivasankar
On Mon, Nov 11, 2019 at 11:10 AM Will Son<EMAIL_ADDRESS>wrote:

@tatag4u https://github.com/tatag4u
Hi,
Thank you for attaching the log.
Have you performed Initial Pose estimation written on eManual?
http://emanual.robotis.com/docs/en/platform/turtlebot3/navigation/#estimate-initial-pose
After map and TurtleBot3 is loaded on the RViz screen, there's a 2D Pose
Estimate button on top so that you can locate the initial pose of the
actual robot in the map.
This has to be done before running the navigation.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ROBOTIS-GIT/turtlebot3/issues/505?email_source=notifications&email_token=AGAXNYBAGNQG3W4PFDM3TALQTDV3ZA5CNFSM4JDOI6XKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDVXCQQ#issuecomment-552300866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGAXNYGQENTSLTVZRXV3XVLQTDV3ZANCNFSM4JDOI6XA
.

Hi
Moreover,that error occurred while loading rviz from navigation.launch file
itself(not during navigation to goal estimate).The same step while I am
doing it in simulation, turtlebot3 is moving to goal.
I have done investigation by calling the launch files(in navigation
.launch) individually. That error is created from amcl.launch file.
Thanks
G.Sivasankar
On Mon, Nov 11, 2019 at 11:10 AM Will Son<EMAIL_ADDRESS>wrote:

@tatag4u https://github.com/tatag4u
Hi,
Thank you for attaching the log.
Have you performed Initial Pose estimation written on eManual?
http://emanual.robotis.com/docs/en/platform/turtlebot3/navigation/#estimate-initial-pose
After map and TurtleBot3 is loaded on the RViz screen, there's a 2D Pose
Estimate button on top so that you can locate the initial pose of the
actual robot in the map.
This has to be done before running the navigation.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ROBOTIS-GIT/turtlebot3/issues/505?email_source=notifications&email_token=AGAXNYBAGNQG3W4PFDM3TALQTDV3ZA5CNFSM4JDOI6XKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDVXCQQ#issuecomment-552300866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGAXNYGQENTSLTVZRXV3XVLQTDV3ZANCNFSM4JDOI6XA
.

Dear Sir
I think transformation is not correct for odom.
What I have shown in attachment is correct transformation ?
Please help me to correct it.
On Mon, Nov 11, 2019 at 11:10 AM Will Son<EMAIL_ADDRESS>wrote:

@tatag4u https://github.com/tatag4u
Hi,
Thank you for attaching the log.
Have you performed Initial Pose estimation written on eManual?
http://emanual.robotis.com/docs/en/platform/turtlebot3/navigation/#estimate-initial-pose
After map and TurtleBot3 is loaded on the RViz screen, there's a 2D Pose
Estimate button on top so that you can locate the initial pose of the
actual robot in the map.
This has to be done before running the navigation.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ROBOTIS-GIT/turtlebot3/issues/505?email_source=notifications&email_token=AGAXNYBAGNQG3W4PFDM3TALQTDV3ZA5CNFSM4JDOI6XKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDVXCQQ#issuecomment-552300866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGAXNYGQENTSLTVZRXV3XVLQTDV3ZANCNFSM4JDOI6XA
.

--
[image: animated-india-flag-image-0004]
With Regards
G.Sivasankar
Assistant Professor(Sr)
Department of ECE
Mepco Schlenk Engineering College, Sivakasi-626005
Ph.+91-4562-235429,09791562538

@tatag4u
I'm sorry for the late reply. Could you point me where I can get the transformation and rqt_graph attachments? Thank you.

This thread will be closed as there wasn't recent activity. Please feel free to reopen when necessary.

Hi
I am getting the error while I am doing navigation topic in turtlebot3 burger using ROS Kinetic on Ubuntu 16.04
[ERROR] [1571763280.542860289]: Couldn't determine robot's pose associated with laser scan
Help me to solve this error? (More specifically while running amcl.launch)
But while doing slam.launch , it is working.

did you solve this problem? if u solved it can you share how you did it ?

I solve the problem by installing the dependency package and increase time
tolerance.
On Fri, Aug 6, 2021 at 12:09 PM Onurcan KARACA @.***>
wrote:

Hi
I am getting the error while I am doing navigation topic in turtlebot3
burger using ROS Kinetic on Ubuntu 16.04
[ERROR] [1571763280.542860289]: Couldn't determine robot's pose associated
with laser scan
Help me to solve this error? (More specifically while running amcl.launch)
But while doing slam.launch , it is working.
did you solve this problem? if u solved it can you share how you did it ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ROBOTIS-GIT/turtlebot3/issues/505#issuecomment-894038866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGAXNYBAUCZQNP3ZUEI7I23T3N7RNANCNFSM4JDOI6XA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

--
[image: animated-india-flag-image-0004]
With Regards
G.Sivasankar
Assistant Professor(Sr)
Department of ECE
Mepco Schlenk Engineering College, Sivakasi-626005
Ph.+91-4562-235429,09791562538

I solve the problem by installing the dependency package and increase time tolerance.
…
On Fri, Aug 6, 2021 at 12:09 PM Onurcan KARACA @.***> wrote: Hi I am getting the error while I am doing navigation topic in turtlebot3 burger using ROS Kinetic on Ubuntu 16.04 [ERROR] [1571763280.542860289]: Couldn't determine robot's pose associated with laser scan Help me to solve this error? (More specifically while running amcl.launch) But while doing slam.launch , it is working. did you solve this problem? if u solved it can you share how you did it ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#505 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGAXNYBAUCZQNP3ZUEI7I23T3N7RNANCNFSM4JDOI6XA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .
-- [image: animated-india-flag-image-0004] With Regards G.Sivasankar Assistant Professor(Sr) Department of ECE Mepco Schlenk Engineering College, Sivakasi-626005 Ph.+91-4562-235429,09791562538

Hi;
Firstly thanks for the reply. I'll try it now but which dependency do you mean?


Marker Animation along a Way

Good day,
We have a fork of iD in which we have added our own features and are using the editor to create simulation scenarios. The simulation takes place in a separate system, but we leverage iD to allow the user to generate the content of the scenario (using the osmChange file that is generated as input into the simulation). While the simulation is in progress, we would like to update the pathways that the user has drawn with a marker showing the current location of a object along those paths (based upon the elapsed time and the speed of the object, which is an attribute of the feature).
This is a great example from openlayers of essentially what we would like to do in iD.
I have tried usingcontext.perform(actionAddEntity())but this adds a new item to the OSM layer and creates a new diff and I am using the differences to iterate through the ways/nodes that need to track the objects for during the simulation. I think ideally I could use a method that would simply draw an icon at a particular geolocation, but if such a method exists I could not find it. There is  function svgIcon(name, svgklass, useklass), however it seems to mostly be used to add icons to buttons in the toolbars/panes and not onto the map layer.
Do you have any insight on how this could be achieved without serious departure from the current  codebase?
Regards,
Tom

Greetings and welcome to the repo, @teiszler. Always great to hear from people using iD in interesting ways.
You're right that adding an entity isn't the best way to show a marker. Unfortunately, iD has been designed for a single user case and so isn't easily extendable, but it should be possible to do what you're talking about.
iD has a number of non-OSM layers loaded by svgLayers. You can insert a new entry here to have the map render it:
https://github.com/openstreetmap/iD/blob/63aa47f02f06534eb3311ec869659cfdffc74f42/modules/svg/layers.js#L25-L40
The layer svgGeolocate is probably the simplest one for you to use as a reference since it just draws a couple circles. It's controlled by uiGeolocate, the button on the right side of the map under the zoom in/out buttons/

Thanks @quincylvania for the quick response. I will take a look at layers.js using svgGeolocate as an example. We have found iD to be fantastic in terms of allowing a user to design a simulation scenario. Originally we were using the existing features that were already present in iD and just coercing them for our use case, but we now have our own custom feature presets that we are using. If I can get the marker(s) to render along the path during the simulation, we can provide visual feedback to the user about how the simulation is unfolding (i.e where each object is along its path), which will go a long way to bridging the gap since the simulation takes place in an entirely separate system.
Best Regards


[FLINK-29982] move the existing Cassandra connector to external repository

Reopening of the previous PR that was automatically closed by github.
R: @zentol

CI is failing due to dependency convergence; we'll need to add a few entries to the dependency management section like we had to in other connectors.

Yes I'm fixing them right now.

@zentol I finished addressing your comments and the CI is green. PTAL

Couldn't sleep so I just started fixing things myself. Squashed all your changes into a single commit.

Couldn't sleep so I just started fixing things myself. Squashed all your changes into a single commit.

Thanks Chesnay for the review and the night merge :smile: I can now more my Cassandra source PR to this repo.


How should fillable interactor work with a disabled input element?

I'm writing a test where I'm testing disabled state of an input element. I'm using fillable to enter value into the input field. If a user wanted to do this, they would not be able to because they would not be able to focus the field. fillable fills out the input because it uses el.setAttribute.
Here is a little example that I made to show this in a react app https://codesandbox.io/s/z6qxxr29mx
Should fillable throw an error if it's not able to focus the element?

I think this is tangentially related to #2 where we want to have validations for interactions. Another example is when a button is disabled. The click event will not fire, but the interaction will not fail.
Since that issue talks more about a11y validations, I think we can keep this open for more general validations

I feel like this is a bug since it'll fill out the input still & probably say the test is passing, right?


Asciimath stopped working in 1.7.0, it works in 1.6.9

Just try
[asciimath]
a+1
The HTML output is $1a+1$2, and the PDF generation cancels.
I had to downgrade to 1.6.9.
I've seen a couple of changes related to asciimath in commit
https://github.com/asciidocfx/AsciidocFX/commit/c33afc626f98c805d0cb205ec32b40e631418a36#diff-f2c6a08f7228ecaf1bd623ea24229fde
Check:

conf/public/js/asciidoctor-block-macro-extensions.js
conf/public/js/asciidoctor-extension-helpers.js.

AsciidocFX is a great product, thanks for your work!

@josemariasola , Hi thanks for reporting :) I'll look it probably next week

code highlighting also stops working in 1.7.0

Hey, try https://github.com/asciidocfx/AsciidocFX/releases/tag/v1.7.1

Hey @rahmanusta
I tried it and asciimath worked like a charm.
Thanks!


CMake files assume that all thirdparty libraries are installed in $CONDA_PREFIX

Per https://groups.google.com/d/msg/gpuopenanalytics/80wqDq0Ap4g/Np1nK8tzAQAJ I would like to see efforts merge around build systems / IPC / reusable analytics kernels for Arrow memory, but in the meantime -- this library can only be built if the required thirdparty libraries (Flatbuffers, Arrow) are installed in a root directory at $CONDA_PREFIX.

Done!

@aucahuasi Could you link to the pull request or changes where these fixes are?

Hi @kkraus14 we will try to make the pull request tomorrow.
For now I just need @williamBlazing or @felipeblazing can check the code.

This is resolved by #56. Closing.


Sort global System usings before other global usings

Fixes #1003

I'm not sure why either of the failed checks actually fail.
Check Formatting seems to fail to something. Locally formatting checks out okay except for the expected after running other tests:
Error ./Src/CSharpier.Cli.Tests/bin/Debug/net8.0/TestFiles/CheckUnformatted.cs - Was not formatted.
  The file did not end with a single newline.
Formatted 302 files in 1254ms.

Without that
dotnet csharpier . --check
Formatted 301 files in 813ms.

Run Tests seems to fail due so some unrelated issue:
 Unhandled exception: System.AggregateException: One or more errors occurred.
 (The process cannot access the file '/tmp/1fd44a6a-9e27-45bb-ad6c-bcaaf578e68d/project.assets.json' because it is being used by another process.)

The tests are actually failing due to dotnet/sdk#35989

@belav can you take a look / update to the latest .net RC? That should fix it.

@belav can you take a look / update to the latest .net RC? That should fix it.

I've been getting past it for now by just running the action again, it usually works the second time. I can hopefully get things updated to the new net8 this weekend.
@vipentti thanks for the fix!


Handle 'strict' keyword.

Change dot parser to record the fact that the 'strict' keyword is
parsed, this will be used when construct the pydotplus.Dot object
after the 'graph' (or 'digraph') keyword is parsed.

Possible solution to issue #6.

While unit tests are failing with this change, I don't think it's related. Unit tests are failing on my system both with and without the change.

Thanks. This will be considered for merging upstream, at: https://github.com/erocarrera/pydot.


automate label for too fresh or extra labels

I've solved this via github bots for now. not sure how we want to document this approach. but i will outlline what i've done below:
Install the following github apps

Triage New Issues - https://probot.github.io/apps/triage-new-issues/
Project Bot - https://github.com/apps/project-bot

Getting Automated triaged issues into a column
created a Card in the Discuss Column on the project board like this:
###### Automation Rules

<!-- Documentation: https://github.com/philschatz/project-bot -->

- `added_label` **triage**

There is also this github app to allow you to have a .github/settings.yml file to define labels and other github settings. seems pretty aligned.
https://probot.github.io/apps/settings/

this looks like it's working for our use case.


[Proposal] 5.3 Tweak (param order in first())

5.3 comes with a change to the ordering of parameters with the method first() on collections - this change is needed:
https://github.com/BenGriffiths/cashier/commit/4cf63e37f2917208af1477bf17cda65591c7d2f2

Submit it as a PR. It's not really a proposal, it's a fix; Cashier in 5.3 just doesn't work because no ->subscription() calls work anymore.

below code in Laravel\Cashier\Billable.php in subscription method should fix it.
return $this->subscriptions->sortByDesc(function ($value) {
            return $value->created_at->getTimestamp();
        })
        ->first(function ($key, $value) use ($subscription) {
            if($key instanceof Subscription) {
                return $key->name === $subscription;
            }
            return $value->name === $subscription;
        });

as its comparing if $key is instance of Subscription(laravel 5.3) else it will consider $value(laravel 5.2)
so it will be backward compitible as well.

Closing this as it's not longer required and sorted in 7.0


Ansible cannot execute the initialization script (permission denied)

Abbiamo eseguito in due ambienti diversi il vagrant up ed in entrambi abbiamo avuto un errore su gli ansible scripts per l'inizializzazione del cluster (sia il master che i workers):
ansible-controller.kubernetes-playground.local: TASK [Initialize Kubernetes cluster (master)]
ansible-controller.kubernetes-playground.local: fatal: [<IP_ADDRESS>]: FAILED! => {"changed": true, "cmd": "/vagrant/scripts/linux/bootstrap-kubernetes-master.sh /tmp/kubeadm-config.yaml calico", "delta": "0:00:00.008279", "end": "2020-01-09 17:23:40.784003", "msg": "non-zero return code", "rc": 126, "start": "2020-01-09 17:23:40.775724", "stderr": "/bin/sh: /vagrant/scripts/linux/bootstrap-kubernetes-master.sh: Permission denied", "stderr_lines": ["/bin/sh: /vagrant/scripts/linux/bootstrap-kubernetes-master.sh: Permission denied"], "stdout": "", "stdout_lines": []}

Il dettaglio con il log completo:
vagrant-overall.log

Hi!
Can you please open a ssh session and run ls -al /vagrant/scripts/linux/ on any of the machines?
Which host systems are you currently using?

ciao Marco may be we have understood: the .sh files are not executable
when we clone the repository, they are not executable and so they are seen as not executable in the /vagrant/... folders both in the master and in the minions

we are using linux host

Let me check. I would understand the error if you were running on a Windows host, because it does not preserve the executable bit.
They have the executable bit set to 1 on my setup...

In the windows host, the +x is added automatically to all files in the shared folders seen by the guests, so there is no problem
Considering that the linux host preserves the file permissions we could add an ansible task that adds +× to all scripts... so we will be on the safe side
Il 9 Gennaio 2020 22:50:45 CET, Marco Ferrari<EMAIL_ADDRESS>ha scritto:

Anyway, to avoid this in the future, I'll add a check in the CI build
and as "pre-flight" checks that run automatically on vagrant up.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/ferrarimarco/kubernetes-playground/issues/20#issuecomment-572772716

--
Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità.

This could not cover scripts that are not executed by ansible. :(


[QUESTION] PlatformResponse/SendResponse middleware

Hi!
After updating from v5.x to v6.x i couldn't find any alternative to
PlatformResponseMiddleware
or
SendResponseMiddleware.
Can you please suggest how to handle such functionality in current version?
Thanks)

Hello @mopcweb
have you read the migration guide?
https://tsed.io/getting-started/migration-from-v5.html#migration-guide
The answer about response middleware is in ^^
see you

Hello @mopcweb
have you read the migration guide?
https://tsed.io/getting-started/migration-from-v5.html#migration-guide
The answer about response middleware is in ^^
see you

Hi @Romakita,
sorry, didn't see that page, i'll look through.
Thanks

Hi @Romakita,
sorry, didn't see that page, i'll look through.
Thanks


Multi-framework coverage for test-suites

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Use preferred tile.openstreetmap.org URL

Use the preferred URL for tile.openstreetmap.org, the old aliases are no longer recommended now that tile supports HTTP/2 + HTTP/3.
Signed-off-by: Grant Slater<EMAIL_ADDRESS>

Link for reference ;-) See: https://github.com/openstreetmap/operations/issues/737


tutorial 3- R and Python

[x] modify R
[x] modify Python
[x] test on dhub
[ ] write notes for users

@MattGrossi-NOAA @EmilyMarkowitz-NOAA Could you test the tutorial 3 R and Python on dhub?
It works for me on my dhub but would like to make sure it works for other users as well.
mahalo!

@MattGrossi-NOAA thank you Matt!
Yes the regionmask didn't seem to be installed yet. I had created an issue for Eli to add it to the packages.
Re: proj warning, we have had that issue. When you run it again, the error disappears.  Will take a look at it.
Thank you!


text animation on first page

https://github.com/codervivek5/VigyBag/assets/95361125/ecbe2e7f-44ab-42dc-a56e-8731c8ffbac3
Add a text animation on the first page where the main heading smoothly fades in and slides up from the bottom. This effect grabs the visitor's attention and provides a dynamic entry experience.

ok let's try but before PR show me the output..if it will relevant then we'll accept your changes

Can I be assigned ?
I really want to work on this issue

https://github.com/codervivek5/VigyBag/assets/120377576/2eec118c-2b2d-4e78-bc39-439ce298b436
https://github.com/codervivek5/VigyBag/assets/120377576/dddaa86c-4d23-441b-9d7c-89f1ca0fd472

looking good... let's connect in seperate place(Discord) where I can tell you more things to make changes.
I will share the official logo then you can use for this...this logo is deprecated now

Can you assign the issue to me

https://github.com/codervivek5/VigyBag/assets/120377576/6e75ef45-9b19-48a9-89d4-b8986e719fd6

can you enhance this ?

and let me know that how will you added it in first page

I will add the file to the repository first then
Watch the video I will replace with the path

Is the animation okay ?

https://github.com/codervivek5/VigyBag/assets/95361125/026fcdf7-7473-4c4b-94b3-8adf34f941f4
simple text animations can enhance the visual appeal of a website more effectively than overloading the entire page with complex animations. Such minimalist effects draw attention to key elements without overwhelming the user, creating a more polished and engaging user experience.


Sources/outputs can't point to a specific path

Describe the bug
Sources and outputs are used as inputs to "globwalk", which does a recursive search for files matching the string. There doesn't seem to be a way to opt out of this, and provide a real relative path.
To Reproduce
Include a config which includes sources and outputs like
[tasks.bug]
sources = [ 'style.css' ]
outputs = [ 'outputs/style.css' ]

This task will always trigger, because outputs/style.css is also included in the last modified calculation for sources.
Expected behavior
It should be possible to specify an actual path, rather than a search path. The behavior and syntax should be clear in documentation. One approach used by some libraries (e.g. glob) is that **/ triggers a subdirectory match.

not surprising, I forgot to test with non-wildcards

Understood 🙂 Not a blocker for me to use, I was just scratching my head over why detection change didn't seem to be working.


sounddevice rec stop playing when silence detected

Hello,
I'm currently using sounddevice to record audio from my speaker output using this code.
import sounddevice as REC
from scipy.io import wavfile
SAMPLE_RATE = 44100
SECONDS = 20
MONO    = 1
STEREO  = 2
REC.default.device = 12
REC.default.channels = 2,0
recording = REC.rec( int(SECONDS * SAMPLE_RATE), samplerate = SAMPLE_RATE, channels = 2)
REC.wait()
wavfile.write('recording.wav', SAMPLE_RATE, recording)

Normally, it should record for 20 seconds but instead if stop at silence before the 20 seconds had finished.
So, for the recorded audio, the length is actually 20 seconds but I get 7 seconds of audio because after 7 seconds there was a silence.
Can you please help me with this issue?
Thank you in advance for your reply.

for the recorded audio, the length is actually 20 seconds but I get 7 seconds of audio because after 7 seconds there was a silence.

I don't understand.
Does this still happen?
If yes, can you please provide more information, including the resulting WAV file?


[Feature request] Fine tuning config for historical sync

Hello,
Since 1.5 landed on the testnet I've managed to reset my backup historical node to test the new historical sync.
It's working fine overall for now however, to speed up the process, I'd like to have fine control over which nodes it connects to for the historical sync.
In my case, I run multiple nodes : 2 mainnet, 3 testnet - 1 one main, one backup historical, and one non-historical.
Given that my node(s) have high-end hardware, it would make sense to make them discuss only between them to sync and change the parameters of the config file to allow more traffic/discussion between them.
Overall, there's always the option to make a backup of a fully synced node and load it on another server, but in the case of exceptional data loss, a month or more to sync historical data is a little bit long. And in a cloud-native environment, it would make more sense to delete a bad node (data loss, database corruption, or anything else) and spin up a new one that will sync from a specified array of nodes.
In the actual config file, we have parameters to protect the node itself, but no parameters to modify the sync speed or anything like that.

This is a VERY specialized case that would likely not be implemented as it introduces fragmentation.  It might be possible to offer nodes that you would like to prefer (like known_addresses).
However, a better solution for your use case is to use the debug socket and the ability to have a shutdown at next block, a certain block, or a certain era.  This can then be used to make an archive and restart the node.  With a file system using checkpoints, the node down time could be a few minutes while the checkpoint was established and then node restarted.  Then this is compressed before the checkpoint is release.  I will be sharing scripts for this as I implement them to make DB archives we use for testing.

I don't think it's a very specialized case because most node operators have multiple nodes. Or on an edge case for Platform As A Service offering Casper Node hosting. I think there's some partners that propose that kind of things.
Especially those affected with the delegators limit and thus may have multiple hot backup nodes to manage also. I've never seen anywhere near 10% ressource usage on my nodes unless spaming some very ressource intensive RPC endpoints.
Obviously the stability is always the priority, but for non validating node would be nice to share those extra ressources to other nodes and a way to priotize a limited set of nodes for historical sync when they need to sync back to genesis.
It's not a feature that is required would be more a nice to have in the future as the state grows etc.


ENG-2084 Add details to settings page about what storage is being used for metadata

Describe your changes and why you are making these changes
This PR adds backend route to fetch global config from server and UI code to diplay on settings page.
Related issue number (if any)
ENG-2084
Loom demo (if any)
File Metadata Storage Information:

GCS Metadata Storage Information:

S3 Metadata Storage Information:

Checklist before requesting a review

[x] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[x] I have performed a self-review of my code.
[x] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[ ] If this is a new feature, I have added unit tests and integration tests.
[ ] I have run the integration tests locally and they are passing.
[ ] I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
[x] All features on the UI continue to work correctly.
[ ] Added one of the following CI labels:

run_integration_test: Runs integration tests
skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

Nice work, @agiron123! The information here looks great, but I think the presentation warrants a little bit of cleanup. In particular, it doesn't look great to show lowercase, unformatted names for things like "gcs" or "s3".
Here's a few things that should be pretty quick but will help quite a bit:

Let's use the logos we already have on the integrations page for each of the storage mechanisms. I know we don't have one for local file storage, so we can use the Aqueduct logo as the default for now.
Let's update the layout to have a little bit more differentiation between the various fields. Here's a suggestion:

[logo]
{Storage Type}

[logo] Bucket:</> {Bucket Name}
[logo] {region && Region:</> {region}}

In case it's confusing, I put logo on multiple lines just because I imagined it would take the full height of the container.

Nice work, @agiron123! The information here looks great, but I think the presentation warrants a little bit of cleanup. In particular, it doesn't look great to show lowercase, unformatted names for things like "gcs" or "s3".
Here's a few things that should be pretty quick but will help quite a bit:

Let's use the logos we already have on the integrations page for each of the storage mechanisms. I know we don't have one for local file storage, so we can use the Aqueduct logo as the default for now.
Let's update the layout to have a little bit more differentiation between the various fields. Here's a suggestion:

[logo]
{Storage Type}

[logo] Bucket:</> {Bucket Name}
[logo] {region && Region:</> {region}}

In case it's confusing, I put logo on multiple lines just because I imagined it would take the full height of the container.
@vsreekanti
Updated Screenshot:

Yep, this is great — thanks!
A few minor nits on top of this:

Let's make the storage type bigger than the rest of the text rather than smaller.
Maybe add a bit more spacing under the "Metadata Storage" header.
Let's use the proper title of the storage engine (S3 rather than s3, Google Cloud Storage rather than gcs).
Using the same techniques we used on the workflow table views, let's differentiate the Bucket/Region keys from their values.

Great work!

Yep, this is great — thanks!
A few minor nits on top of this:

Let's make the storage type bigger than the rest of the text rather than smaller.
Maybe add a bit more spacing under the "Metadata Storage" header.
Let's use the proper title of the storage engine (S3 rather than s3, Google Cloud Storage rather than gcs).
Using the same techniques we used on the workflow table views, let's differentiate the Bucket/Region keys from their values.

Great work!

@vsreekanti I've added a follow on task to address here:
https://linear.app/aqueducthq/issue/ENG-2506/storage-metadata-design-feedback


Bug: Press Enter on a Move with Prompt Refresh

In GitLab by @brunocalado on Mar 22, 2021, 18:21
Bug: Press Enter on a Move with Prompt Refresh
If you press the key Enter at a move with Prompt it'll refresh foundry instead of roll.

Labels (do-not-change)
/cc @Asacolips

In GitLab by @Asacolips on Jun 22, 2021, 17:33
Resolved in beta8-0.2.0


Add support for SPOP with a count argument

This PR adds support for the count part of SPOP key [count] that was introduced in REDIS 3.2. The implementation follows the implementation of SRandMemberN.

Thanks!


applied correct builder terminology,and some minor grammar edits to o…

…nboarding
@xavijam , just edited some terminology to the onboarding text to be consistent with the UI guidelines that were created. @namessanti for awareness.

@noguerol, I feel this is your call.


Modin release 0.11.0

subj. Fixed recipe for conda-forge.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


When rulePath is missing, error notification appears on every file edit

Every now and then, our custom ESLint rules directory goes missing for some reason, and fixing it would generally not be my absolute top priority that needs to interrupt everything else. Except, it is, because the extension makes it impossible to focus on anything else in VS Code until it’s taken care of:

Screen capture

The reason for this is that the ESLint server has no idea about the severity of such an error. What we can do is to add a 'Ignore for this session' button.


fix-bug

Codecov Report

Merging #115 (5556697) into master (4c7ab6f) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #115      +/-   ##
==========================================
+ Coverage   95.15%   95.18%   +0.02%
==========================================
  Files           7        7
  Lines         351      353       +2
==========================================
+ Hits          334      336       +2
  Misses         17       17

Impacted Files
Coverage Δ

service/routes.py
95.23% <100.00%> (+0.07%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Marking unread notification

Kindly add a button to all unread notifications as read, like mark all as read.

Hey, this is something I've thought about but it's not in my needs right now so I likely won't get to add it just yet.
If you are needing this functionality sooner rather than later though I'll gladly accept a PR for it.

@Boomchart titonova/megaphone has implemented this


incompatibility between oneshot and overload when defining shift and some letter

These two instructions are exclusive since when I use shift with any other letter it behaves properly, however when I use it with the letter a it continues to be written in lowercase:
shift = oneshot(shift)
a = overload(meta, a)

Thanks, this was indeed a bug. I just pushed a fix, but it is probably worth noting that you will run into other problems with overload(meta, a). You probably want overloadt (which doesn't suffer from this problem) if you are going to overload letter keys.


Add PSCI driver

A bit of rationale behind this PR.
@MrVan submitted in #30676 the PR to enable SMP on AArch64. As I wrote in a review to that PR I do not particularly like the approach of using arch-specific code to interface with the PSCI firmware.
PSCI interface needs a proper driver that uses the DTS to detect the correct parameters, especially the conduit (and currently only that). This is particularly important because the choice of having SMC or HVC as conduit really depends on whether we are running an hypervisor or not in EL2, so this must be something configurable at DTS (board) level.
So here it is a proper PSCI driver with support  for PSCI 0.2 and PSCI 1.0, enabled using the DT and also a tiny test to make sure that everything is working correctly.

@carlocaione Thanks for adding psci support, your code looks good to me. Approved.

Can we merge this?

Can we merge this?

Overall looks great but it would be better to have code coverage of the syscalls by running the test function in user mode, and have the test exercise all of the APIs.

@andrewboie I addressed your points. The only API I couldn't test was psci_cpu_off (because that actually shuts the CPU off).

Overall looks great but it would be better to have code coverage of the syscalls by running the test function in user mode, and have the test exercise all of the APIs.

@andrewboie I addressed your points. The only API I couldn't test was psci_cpu_off (because that actually shuts the CPU off).


renaming target value to validation target value, adding test targets

Ha, thank you so much for catching the typos!


Add the Ability to use multiple explorers/daemons to j.clients.blockchain.rivine

Ha for light clients is achieved by using multiple explorers/daemons. In case one  is down another  one can be used.

fixed by 432053

fixed by 432053e

In [14]: from JumpscaleLib.clients.blockchain.rivine.RivineWallet import RivineWallet

In [15]: wallet = RivineWallet(seed=seed, bc_networks=['https://exploer-unreachable.com','https://explorer.testnet.threefoldtoken.com/'],bc_network_password='test123',nr_keys_per_seed=5,minerfee=100000000)

In [16]:         wallet.current_balance
[Thu06 11:38] - utils.py          :89  :lockchain.rivine.utils - WARNING  - Failed to get current chain height.
[Thu06 11:38] - utils.py          :174 :lockchain.rivine.utils - WARNING  - Failed to retrieve unconfirmed transactions.


made initial changes for keycloak auth

https://koverse.atlassian.net/browse/KDP-XYZ
why does this matter?

CHANGEME

what was impacted?

CHANGEME

how do you know this works?

CHANGEME

how does this make you feel?

Going to close this PR, as I have another PR on a branch including these changes.


(2.4.1) Hauling job order not working as intended

IMPORTANT: Please first search existing bugs to ensure you are not creating a duplicate bug report!
Describe the bug
Colonists will iddle instead of hauling.
Steps to reproduce the behavior (VERY IMPORTANT)

create a new colony
create a dumping zone
mark boulders to be haul off the way
colonists will not do the hauling job

Error Log
no red errors for this one
Save file
SaveFile is attached
hauling not working.zip
Screenshots
!!! Add screenshots to help explain your problem here !!!
Mod list (For vanilla report, it has to be same as below list.)

Harmony
Core
Royalty (optional)
HugsLib
RimThreaded

issue fixed on 2.2.11 preview

reopening this one after a working session with @cseelhoff
here's the save file
hauling test.zip

should be fixed now


presence updates

adds presence update support + some convenience methods inside the Catnip interface
note: i had to pull off a minor quirky thing which is presence updates being sent on random shards, as it's impossible to know which specific shard to use from just using the Catnip interface. it does work and is tested tho so 👌

why not broadcast the presence update to all shards, with an optional method to update on only one shard?

i'll probably add a method parameter (default = false). when true it broadcasts to all shards. seems kinda overkill to broadcast the update to every last shard when there's only one Catnip instance

each shard has it's own presence, if you only send to one members on the others won't receive the updates

Oh i c i c, i'll do the opposite then (default = true)

alright i think this is good to merge now
closes #54 and #55 and provides a PresenceBuilder as well as convenience methods to make this approach easier for ppl actually using presence updates

everything is done now afaik. there's still the unrelated issue of having to find out the id of the current shard but yea 👏 👌


SA1009 and C# 7 Tuples

SA1009 is indicated at the closing brace of tuples inside generics. For example for the following function definition:
internal override async Task<(bool doReplace, string replacement)> TryCorrectPostBody(string postBodyValue)

In my opinion, this use case should be allowed and no SA1009 generated.

Yeah, we need to evaluate all new C# 7 syntax in the context of current rules.
@vweijsters @pdelvo Any thoughts on how to start testing these scenarios? We could create a unit test project that references a version of Roslyn that understands C# 7, or we could use a different version of Roslyn for the main library and the unit tests. Or perhaps we create a new "v2.0" branch where we require such a version of Roslyn, and don't accommodate these features in the 1.x branch at all?

See also #2268

I would be in favor of having a branch, as we will probably have to do some major changes to the analyzers, the code fixes, and the unit tests. I haven't checked yet, but I assume that the new language constructs will have new syntax classes as well, and these will not be present in older versions.
I personally am not a big fan of having a lot of #if directives in code, which would probably be needed to accommodate both versions of Roslyn from a single code base.
We may need to maintain two versions of the project in parallel for (quite) some time, I'm not convinced yet that we can merge the code bases for these, but that could change once we've done the work for v2.0.


Refactoring of IndexFirebaseArray

Hello,
I had a look at your PR and came up with some refactoring of IndexFirebaseArray:

It makes use of original mSnapshots from FirebaseArray
There is only one ValueEventListener listener instead of a map
I got rid of mNullableSnapshots
It uses most of super implementation for ChildEventListener, with a trick to mute the original OnChangedListener listener from being notified when something with keys changed on super methods:

    super.setOnChangedListener(null);
    super.onChildAdded(keySnapshot, previousChildKey);
    super.setOnChangedListener(mListener);

In addition I think that this class should be renamed to FirebaseIndexArray to be more consistent with names like FirebaseIndexListAdapter or FirebaseIndexRecyclerAdapter.
Please tell what do you think about that.
Cheers!

@SUPERCILEX Thanks for your replay!
I've added a check if value in dataSnapshot is null.
Regarding mNullableSnapshots I don't think it is needed since the the mSnapshots from FirebaseArray is used now to calculate indexes, which I think is more elegant solution.
mDataSnapshots (in IndexFirebaseArray) contains only non-null items, which is a subset of all items stored in mSnapshots (in FirebaseArray). In other words mNullableSnapshots would be like a join of mSnapshots (containing all of keys) and mSnapshots (containing only non-null items).

I had time today to really look at what you did and how you got rid of mNullableSnapshots. Thanks, it's awesome!
I did a bunch of cleanup (including remove all the super calls) and fixed a bug because you called super.onChildRemoved(keySnapshot) before getIndexForKey(key). Anyway, take a look at what I did and if you're happy with it, send me a 👍 and I'll merge #11.

Oh well, I guess we'll have to go with the supers for the time being... I'll ask @puf if he has any ideas. Send me a 👍 and I'll merge.

@SUPERCILEX There is always alternative way by using a flag to temporary avoid notifying the listener:
private boolean mDoNotNotifyChangeListeners;

...
@Override
public void onChildChanged(DataSnapshot snapshot, String previousChildKey) {
	mDoNotNotifyChangeListeners = true;
	super.onChildChanged(snapshot, previousChildKey);
	mDoNotNotifyChangeListeners = false;
}
...

@Override
protected void notifyChangedListeners(OnChangedListener.EventType type, int index, int oldIndex) {
	if (!mDoNotNotifyChangeListeners){
		super.notifyChangedListeners(type, index, oldIndex);
	}
}

Quick facts:

There are no super calls here (but they do not really bother me)
We can remove local mListener
Remove overriding of setOnChangedListener
Now notifyChangedListeners is overriden
It introduces an extra variable. with local mListener it uses only something that already existed in super implementation.
The end result is the same

Since IMO this is a matter of elegance and feeling we should ask @puf which solution is nicer in his opinion.


remove unchangable fill algorithm option

It was changeable, using the CLI

which nobody seriously uses, but the bigger problem is that this just gets enabled if some bits of a permalink line up badly, and there is no warning or anything


Web UI glitch

Hi,
I've noticed a small but annoying bug on the admin web UI.
Using the latest 2.8.9 version from the docker image.

go to 'Graphs'
click 'Add Graph'
click inside 'Edge definitions', pick one
click again inside 'Edge definition', a drop down with the text 'You can only select 1 item' appears
hit 'Cancel' button

=> the dropdown does not disappear, see screenshots below. The only way to get rid of it is to refresh the page.

Thank your for the report. Issue is fixed in current devel branch and will be included in the upcoming 3.0 release.


WIP: gettext: refactor and split in multiple packages

Motivation for this change
This PR solves  #73288
Following upstream recommendations, gettext is split into 3 distinct
packages:

gettext-runtime
gettext-tools
libtextstyle

See https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=blob;f=PACKAGING;h=f4bae4561ec70a9de2532502b5c2358bb976036c;hb=55b8fe9a2f12b22eb3ee6baf973e03e60b3a9915
Given that for each sub-package we use sourceRoot, the patches do not
apply directly when fetch from upstream git and have to be editted to
strip the top level dir.
For the time being, gettext is turned into an alias to
gettext-runtime to ease transition.
A tree-wide update could be tried to replace all occurances of a gettext dependency with gettext-runtime if required by review.
I am also very open to discussions on how I did implement the 3 packages that share 1 source tarball.
If we are too close to the last staging changes before release-20.03, I have no problem to postpone this MR (cc @FRidh ).
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

@jtojnar thanks for the review
I am so ashamed of the number of of typos I did let through…
I am rebuilding everything to test at the moment. I’ll push when I have checked that it builds properly.
I have also ported some modifications you suggested from gettext-tools to gettext-runtime (like drop trying to drop CFLAGS=-D_FORTIFY_SOURCE=0 for darwin). hydra will let us know if this is a mistake. If necessary it will be easily to reintroduce.

For the time being, gettext is turned into an alias to
gettext-runtime to ease transition.

Looking at the tree, gettext should probably be alias of gettext-tools since things depending on it usually just need msgfmt.

The setup hook should probably be split as well. GETTEXTDATADIRS is used by xgettext and msgfmt IIRC, while the LDFLAGS stuff sounds like it would be runtime thing? IDK.

Yes, some packages build do require (explicitly) msgfmt.
Do we have a simple way to have a “old style” gettext dependency translate into gettext-runtime as a buildInput and gettext-tools as a nativeBuildInput ?
I am not sure of a nice way to approach that :thinking: suggestions ?

Everything build using meson at least. And instltool should propagate msgfmt. I would be surprised if anything used the runtime.

I would actually suggest going with gettext = gettext-tools; and letting Hydra tell us what is broken. And then based on that add the runtime where needed. And finally resolve the alias.

@jtojnar I am a but busy at the moment, I’ll come back to this MR probably next week and try to make progress on it.
Thanks for your feedbacks, they are really valuable!

Still interested in this @lsix and @jtojnar?

Yes, we definitely still want this but I do not think I will be able to finish this for 20.09.

Yes, we still want this, but I have not had much time nor build resources to dedicate to it :sob:

It's been a while—will you ever revisit this?


undefined: uint56

What version of Go are you using (go version)?

$ go version
go version go1.16.3 linux/amd64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/dual/.cache/go-build"
GOENV="/home/dual/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/dual/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/dual/go"
GOPRIVATE=""
GOPROXY="https://goproxy.cn,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.3"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/dual/code/golearn/http-sender/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2014177637=/tmp/go-build -gno-record-gcc-switches"

What did you do?
go build .

src :
package main

import (
	"fmt"
	"io/ioutil"
	"log"
	"os"
)

func main() {
	stat, _ := os.Stdin.Stat()
	fmt.Printf("%#v\n", os.ModeNamedPipe)

	fmt.Println()
	str, err := ioutil.ReadAll(os.Stdin)
	if err != nil {
		log.Fatal(err)
	}
	fmt.Println(string(str))
}

What did you expect to see?
go build no errors
What did you see instead?
run time error
runtime
/usr/lib/go/src/runtime/select.go:44:44: undefined: uint56
select.go
func selunlock(scases []scase, lockorder []uint56) {
	// We must be very careful here to not touch sel after we have unlocked
	// the last lock, because sel can be freed right after the last unlock.
	// Consider the following situation.
	// First M calls runtime·park() in runtime·selectgo() passing the sel.
	// Once runtime·park() has unlocked the last lock, another M makes
	// the G that calls select runnable again and schedules it for execution.
	// When the G runs on another M, it locks all the locks and frees sel.
	// Now if the first M touches sel, it will access freed memory.
	for i := len(lockorder) - 1; i >= 0; i-- {
		c := scases[lockorder[i]].c
		if i > 0 && c == scases[lockorder[i-1]].c {
			continue // will unlock it on the next iteration
		}
		unlock(&c.lock)
	}
}

Something is wrong with your source code.  The line in the actual 1.16.3 sources is https://go.googlesource.com/go/+/refs/tags/go1.16.3/src/runtime/select.go#44.  As you can see, the real sources use uint16, not uint56.  Somehow in your source code the 1 has changed to a 5, which is a single bit error in ASCII.  Either something modified the file, or your storage system had an undetected single bit error.
Closing because this is not a problem in Go.


where to include rtl files

For verifying a processor you have done software simulation using imperas and hardware simulation is done and then the log files are compared. Can u pls give me an idea of how to include the RTL files for verifying the processor and how the hardware simulator is done?

The README in https://github.com/riscv-non-isa/riscv-arch-test/ doc directory should include the information you need.
Have read it and found something missing?

I have not hear a response, so I'm closing this. Reopen if you still have an issue.


What mod is that translation for?
Smelter
Additional Comments
I made Polish Translation, maybe its working.
I also have two suggestions about mod:

Can we get melting Plastic to Naphta Recipe in Glass Forge?
Can you add Melt Sulfur to Liquid Sulfur Recipe?

translation file
polish translation.zip

Thank you for contributing


Sync relationships by only providing the id

Today to sync a relationship you need the full JSON object. This is because Sync prefers to make sure that if the object isn't found in Core Data, it will just add it to Core Data and link it to the necessary objects.
For example if you had a list of projects that had a category inside (Project -- to one --> Category) the JSON should look like this:
{
    "id":12345,
    "name":"My Project",
    "category":{
       "id":12345,
       "name":"My category"
    }
}

But if you are super sure that the category already has been inserted in Core Data and is not going to be removed while the sync operation is in progress you should be able to just send.
{
    "id":12345,
    "name":"My Project",
    "category_id":12345
}

The requirement of the full JSON object from Sync comes from the fact that it ensures that the required category object will exist at all times, sadly not all the APIs work this way and they choose to remove this since it causes data repetition.
Related to #139 and #64.

We could add a flag to the user info in the relationship, to clarify that only the ID has been provided.
Maybe something like hyper.justForeignKey : YES

Where would be the best place to add this change?  My first guess is to add a function like sync_processToOneRelationship that only takes an id.  The function would only be called when "hyper.justForeignKey : YES" was set.  Then I can reuse sync_safeObjectInContext and add the relationship.

@tpmullan

break backwards compatibility

I meant that if today there are people using category_id to just store the category_id then it could break, but we could just find a way to not break it. :)
Right now I'm trying to figure out the other case scenarios.
1.- We have two entities: User and Category. Each category has an id and a name, each user has an id, a name and a category_id.
Here it would be easy, you first sync all your categories, then when you sync your users the categories will just get mapped. If you do it the other way (first sync users then categories there's nothing we can do, that was probably what I didn't like about this system).
2.- We have one entity: User. Each user has an id, a name and a category_id.
Here the elements get mapped, relationships don't get made.
3.- This is similar to number 1, the difference is that a user can be part of many categories. We have two entities: User and Category. Each category has an id and a name, each user has an id, a name and a category_ids (an array).
Here it would be easy, you first sync all your categories, then when you sync your users the categories will just get mapped. If you do it the other way (first sync users then categories there's nothing we can do, that was probably what I didn't like about this system).

Test models with multiple letters

Right now number 1 is being added and tested, I even added test for entities that have multiple words so: "ChallengingGoal" gets mapped to challenging_goal_id, if you do lowercase then it gets changed to challenginggoal_id which is not what we want.

Case number 2 should work fine in the current setup but I would like to add a test for it. Then I'll have a look at number 3, then let this feature cooldown for a bit on master and make a new release next Friday.

Good set of edge cases.  The way I structured my data made it work for me, but it wasn't very generic.  I will test your version this week.  Thanks!

Might be interesting to handle a special case for people that have category instead of category_id.

Is this already available in the current release?

@violabg Only on master.

I made a separate issue for the to-many mapping. https://github.com/hyperoslo/Sync/issues/151
Closing this.

I also improved the README so it shows that this is possible.
https://github.com/hyperoslo/Sync#relationship-mapping

This is included on 1.3.0 now
https://github.com/hyperoslo/Sync/releases/tag/1.3.0

Thanks for the reply.
I can't figure it out the way to structure my json in order to be converted to my model.

basically I have a list of languages and categories, plus a list of Brochures that are group by language and category.
could you help me understand what kind of json I would need in order to achieve this, or if it is possible at all?

@violabg please make a new issue for this.

@violabg I made a new issue for this https://github.com/hyperoslo/Sync/issues/152


Issue from website page Get Started: Overview

From URL: https://flutter.io/get-started/

Is there actually an issue? Can you please provide more details?


sanitycheck: samples: net: echo_server: Doesn't run all configurations from atmel_rf2xx shield

Describe the bug
Inspection on buildkite 2/20 from #26655 reveals that not all configuration have been built. I suspect that boards that don't have a netif interface will not build/run with shields. This need more inspection to make sure it is not affecting more configurations.
To Reproduce
Clone main repository and run ./scripts/sanitycheck --testcase-root samples/net/sockets/echo_server.
It seems to run even less combinations.
Expected behavior
All configurations should run and must build all combination at buildkite to ensure that CI is OK and Zephyr cover all test scenarios.
Impact
Many configurations may not be running as expected and we can accept broke code.
Logs and console output
1- Goto https://buildkite.com/zephyr/zephyr/builds/2728#8c66b445-9f4f-41ed-a431-3c8769e3247e
2- Search by rf2xx and check builds 76 up to 93.
3- Confirm that below configurations hadn't build:
3.1 - sample.net.sockets.echo_server.802154.rf2xx
3.2 - sample.net.sockets.echo_server.802154.rf2xx.xplained
3.3 - sample.net.sockets.echo_server.802154.rf2xx.mikrobus
Environment (please complete the following information):
Current Buildkite CI
CC: @nashif @jukkar

All configurations should run and must build all combination at buildkite to ensure that CI is OK and Zephyr cover all test scenarios.

This is not the expected behavior, we do not build everything and all combination, this is done on a nightly basis, but not per PR.

Hi @nashif
Maybe I not expressed my self on a clear way. When I wrote "all configurations" I'm referring at sample/test with a whitelist. So, not all whitelist combination are building. In this case, I created combinations to make sure that a change on that overlays + SoCs are Ok on a minimal set. Those are the minimal build set that should pass on CI when a PR is sent to cover all code variations. Otherwise, code can be changed and not compile, however PR can be accepted as OK.
For instance, on my view the below fragment should build on CI, but it is not.
  sample.net.sockets.echo_server.802154.rf2xx.mikrobus:
    extra_args: SHIELD=atmel_rf2xx_mikrobus OVERLAY_CONFIG="overlay-802154.conf"
    platform_whitelist: lpcxpresso55s69_ns

I'm raising this because I've been seen code changes that not even built but PRs were accepted as OK. Than people start to open issues. This could create a feeling that CI is not trustworthy, and that kind thing I'm trying to avoid opening this PR.

CI not cover all paths, see #28341

the one is not building in CI because the testcase depends on netif, this board does not provide it, so this:
diff --git a/boards/arm/lpcxpresso55s69/lpcxpresso55s69_ns.yaml b/boards/arm/lpcxpresso55s69/lpcxpresso55s69_ns.yaml
index a78352ecf7..fb91153a41 100644
--- a/boards/arm/lpcxpresso55s69/lpcxpresso55s69_ns.yaml
+++ b/boards/arm/lpcxpresso55s69/lpcxpresso55s69_ns.yaml
@@ -19,3 +19,4 @@ supported:
   - gpio
   - spi
   - watchdog
+  - netif

would make it at least buildable...
However, you then hit the next problem that the test/app itself does not fit on the board, so it overflows. None of this is a bug of sanitycheck, this is just test configuration.

Hi @nashif , this helps a lot to understand the problem but not solve them. The boards that are using shields could never set the depends on at yaml file. Why? These are are shields and can be used on any board extra_args: SHIELD=atmel_rf2xx_mikrobus OVERLAY_CONFIG="overlay-802154.conf".
Are there any way to address the depends on for shields? How shields can expose "netif", "ieee802.15.4", etc for instance? I'm asking because I don't see any *.yaml on shields directory and I'm not sure about it.

Can you please stop reopening this as a high priority bug, it is not a bug and it is not a high priority one for that matter.
Please open an enhancement request with the support you are looking for, this is going to be fixed probably with https://github.com/zephyrproject-rtos/zephyr/pull/25703 when it lands, then the filter would work on DTS and what the shield provides.

Hi @nashif , sorry if I'm disturbing, this is not my intention. Now I have a good picture about what is happening and how things will move forward.
Thank you!


Nissan port

Nissan port. Should be pretty much complete. Open to comments/suggestions

@avolmensky can you add a route to test_car_models.py? we'll take care of uploading the route so the regression test will pass.

@avolmensky , the port looks pretty clean. I recommend re-basing with master and apply the changes to make it look like the other ports. There has been quite a bit of work during the last 2 weeks to simplify the car port code and those changes should apply to this port too before it gets merged. After those changes, this PR should be 100-150 lines shorter.
@pd0wm , once all the tests pass and the changes mentioned ^^ are done, I recommend merging this PR into openpilot and force it in dashcam mode (like Ford) until verified.

@avolmensky , not that you can preserve routes from useradmin, you should be able to fix the failing tests I think.

A couple of minor comments and tests that need to be fixed, then we should merge this PR in dashcam only mode. Almost there :)

Thanks for the work on the port! Comma will rent a Nissan soon and do some final testing.
Don't worry about conflicting files, we can take it from here.

Dear all, I would like to adapt open pilot for a 2013 Nissan Serena. Will this port.py file help me in any way? I am a beginner and new to the community so sorry if I am commenting at the wrong place. I will delete if this is in-apropriate. Many thanks
Clement


"rakudobrew build panda" fails if PERL5LIB env var is set

On a completely fresh install of of rakudobrew, I get this:
$ rakudobrew build panda
<snip>
==> Bootstrapping Panda
==> Installing panda from a local directory '/Users/curtispoe/.rakudobrew/moar-nom/panda'
==> panda depends on File::Find, Shell::Command, JSON::Fast
==> Shell::Command depends on File::Find
==> Fetching File::Find
==> Building File::Find
==> Testing File::Find
Perl v6.0.0 required--this is only v5.18.4, stopped at lib/File/Find.pm line 1.
BEGIN failed--compilation aborted at lib/File/Find.pm line 1.
Compilation failed in require at /Users/curtispoe/perl5/perlbrew/perls/perl-5.18.4/lib/site_perl/5.18.4/App/Prove/State.pm line 6.
BEGIN failed--compilation aborted at /Users/curtispoe/perl5/perlbrew/perls/perl-5.18.4/lib/site_perl/5.18.4/App/Prove/State.pm line 6.
Compilation failed in require at /Users/curtispoe/perl5/perlbrew/perls/perl-5.18.4/lib/site_perl/5.18.4/App/Prove.pm line 10.
BEGIN failed--compilation aborted at /Users/curtispoe/perl5/perlbrew/perls/perl-5.18.4/lib/site_perl/5.18.4/App/Prove.pm line 10.
Compilation failed in require at /Users/curtispoe/perl5/perlbrew/perls/perl-5.18.4/bin/prove line 8.
BEGIN failed--compilation aborted at /Users/curtispoe/perl5/perlbrew/perls/perl-5.18.4/bin/prove line 8.
test stage failed for File::Find: Tests failed
  in method install at /Users/curtispoe/.rakudobrew/moar-nom/panda/lib/Panda.pm line 156
  in block  at /Users/curtispoe/.rakudobrew/moar-nom/panda/lib/Panda.pm line 228
  in method resolve at /Users/curtispoe/.rakudobrew/moar-nom/panda/lib/Panda.pm line 222
  in sub MAIN at bin/panda line 18
  in block <unit> at bin/panda line 150

However, it works just fine when I clear my PERL5LIB environment variable:
$$ PERL5LIB= rakudobrew build panda
Already on 'master'
Your branch is up-to-date with 'origin/master'.
==> Bootstrapping Panda
==> Installing panda from a local directory '/Users/curtispoe/.rakudobrew/moar-nom/panda'
==> panda depends on File::Find, Shell::Command, JSON::Fast
==> Shell::Command depends on File::Find
==> Fetching File::Find
==> Building File::Find
==> Testing File::Find
t/01-file-find.t .. ok
<snip>
Updating shims
Done, built panda for moar-nom

Hmm, I just attempted that on 2016.03 and it worked without fail. Is it some particular rakudo version/PERL5LIB value that may cause this for you?

Panda is long dead. There is a slight chance this still happens on build-zef, but looking for a bug that's most probably not present is a waste of time. So I close. Please reopen if you happend to hit this again.


Also scrape timestamps from all tables scraped from MOH

MOH has begun adding text indicating when pages and tables are updated. Scrape them also and include them in the API and metrics.

Looking forward to this feature. This is what I was thinking about, but haven't reached that point for my app. (btw hope not affects the original apis)

Or is it possible to monitor the API to see when the data changes?
e.g: for my app, it is the timestamps when your API updated, not the timestamps MOH publish something.

@shawyunz as with my response to the other issue - I recommend pulling the arcgis.com JSON layers, as now described in the README. Cheers!


[Question] SetStatus

The new "setstatus"-Feature is overriding the Status constantly. I want to have it on DND, but it will override to ONLINE again till I stop the bot (I'm not using the "setstatus"-command). And could you add a config-entry to let the bot Change the Status on Startup?

Adding a default status to the config is definitely possible.
As for the other part of the question... how are you setting the status without using the setstatus command?

I'm using a second bot to handle that.
I have edited your bot to "not using" the "**censored because of a global-post **" - method.
It seems to work now to change the Playing-Status and the status..
Maybe you could create another config-entry too,
for example: "dont-use-status-system" to disable the overriding of this!

There is no such thing as "overriding" a status; every single connection to Discord must have a status. Some statuses just take priority over others. To prevent what you call "overriding" you need to set the music bot to invisible.
If you're editing the bot, please don't post issues here. I realize that your issue isn't necessarily related to your edits, but I won't provide support for edited versions.

It's not really an issue. And I'm aware that your won't give support of edits (bc I read stuff :P), but as you said, it has nothing to do with "supporting". It's like just giving you feedback or information of something. I didn't think about setting it on invisible! But for now the official version will "Not work", because of it's missing feature, as I said previously. (Auto-Restart) Btw, as I know so far, "Type " is the default status, which is set, if the config-entry is null? If setting to "none", it will completly empty it. Or is both the same?
If you don't want this type of conversation in this section, we can continue to write private if you want!

I'm using a second bot to handle that.

What bot is this?

I'm using a second bot to handle that.

I'm not advertising another bot here.

The config and command from the latest release should cover this, feel free to re-open if it still doesn't cover what is needed here.


The temporary tab doesn't become permanent if moving its split tab to the temporary tab view for one ADLS Gen2 blob container

Storage Explorer Version: 1.24.0-dev
Build Number: 20220421.6
Branch: rel/1.24.0
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Monterey 12.3 (Apple M1 Pro)
Architecture ia32\x64
How Found: From running test cases
Regression From: Previous release (1.23.1)
Steps to Reproduce

Expand one ADLS Gen2 storage account -> Blob Containers.
Select one blob container -> Click it to open a temporary tab.
Split the tab -> Move the split tab to the temporary tab view.
Check whether the temporary tab becomes a permanent tab.

Expected Experience
The temporary tab becomes a permanent tab.
Actual Experience
The temporary tab doesn't become a permanent tab.
Additional Context
This issue only reproduces for ADLS Gen2 blob containers.

Actually, I noticed that dragging a tab to the spacer area to clone the tab is broken. I will address that as well when fixing this issue.

Verified this issue on the build 20220424.1. Fixed.


Counterparty Behind Bitcoin

What's the recommended strategy for something like this, I encountered in 10.4.5 and it persisted in 10.4.8, should I rollback and see if it resolves? I've run into this a few times this year and I'm never really sure what to do about it.
The API shows:
{
"result": {
"server_ready": false,
"network": "mainnet",
"version": "10.4.8",
"backend_height": 866102,
"counterparty_height": 866077,
}
}

Command line:
[INFO] - Catch up complete.

Interestingly the counterparty_height is going down when I refresh this api endpoint...
{
"result": {
"server_ready": false,
"network": "mainnet",
"version": "10.4.8",
"backend_height": 866102,
"counterparty_height": 866074,
}
}

Maybe there's some processing happened that's not reflected to me in the journalctl which looks just like it's watching the mempool all caught up.

Two nodes that I've upgraded are like this, their height it going down slowly one block at a time and the logs on the command line just look normal. Now it's down to 866,070.

Nothing in the logs, just seeing the height slowly roll back now at 866,064.. 866,604.

I had rolled back to 865690 prior to updating, maybe it's a weird interaction of the two.

yeah this is weird. will investigate

It seems to have stopped at 866,050, but I can't be sure until more time passes.

Rolled backed, it caught back up, at least in my command line logs, but still showing 866,050. Could be some sort of caching or the ledger_hash isnt being populated on blocks so the query isnt selecting the latest or i dont know what. I may fully reparse.

I'm thinking it's to do with this relatively new change that adds a ledger_hash condition to the selection query:
https://github.com/CounterpartyXCP/counterparty-core/blob/34d4436c67e360fb73cf7479bc80b0e6d4b09692/counterparty-core/counterpartycore/lib/ledger.py#L1133-L1144

So bizarre, I went to dinner and it was resolved.


Move use-program caching to cepl-context

Each thread binds separately so current use-program cache breaks in our multi-context branches.

Done :)


CPU vs CUDA time

Hi all, a newey here.  I wanted to ask for some help regarding the reported CPU and CUDA processing times. Can some one explain to me what is the difference between them? Thanks in advance.

Hi @egamezl, the CPU time is the wall-clock time while the CUDA kernels are launched on GPU and the CPU is idle waiting for GPU to finish.  The CUDA time is the time that the GPU actually spend processing the kernels.  In general the CPU time will be slightly more than CUDA time, since there is some lag/overhead to launch the CUDA kernels and wait for them to finish.
There may also be times when the CPU is doing additional processing, for example in object detection models the CPU does the bounding-box clustering.  So the CPU time would be higher in that case.

Hi @dusty-nv , thanks a lot for the quick answer. It makes sense to me, specially that CPU time should be slightly higher that CUDA time.
The question came from running detectnet script and looking at the resulting times, here I am constantly seeing higher CUDA times. Since this program detects objects, it is the case of your last statement, right? Thanks again.

The question came from running detectnet script and looking at the resulting times, here I am constantly seeing higher CUDA times.

Some of the kernels don't require CPU synchronization.  For example, during visualization step, CUDA draws the bounding boxes over the image, and the CPU doesn't need to wait for that result because the CPU doesn't directly use the contents of that image.  So the CPU time is low because the CPU just keeps going onto the next step.
However in the network step, CPU needs to wait for GPU after, because CPU needs the results of the bounding boxes so it can cluster then during the post-process stage.   Hope that makes sense.