Unable to create 3D map with OAK-D

I am using ROS1 Ubuntu 18.04 ROS Melodic. Unable to create a 3D map with OAK D when launched with Rtabmap with all the arguments as mentioned in Rtabmap stereo handheld mapping, I am using MPU9150 imu. I am also having a transform link between oak_d-frame and base_footprint. I am using stereo_inertial_node.launch file of depthai-ros package for launching OAK D camera. Any help or solution regarding this problem is appreciated.

Thank you

Let me know if this helps.

Thank you for your response @saching13 but that is not working for me. I am using the same updated bringup and rtabmap launch for OAK-D stereo mapping which is mentioned on this website. http://wiki.ros.org/rtabmap_ros/Tutorials/StereoHandHeldMapping
I tried two OAK-D cameras separately, one with IMU and one without IMU but still, it gives the same error in both cameras.

Thanks. Will check on our side and get back to you.

Sorry was not able to get it to working. looks like there are internal issues on Rtabmap. Need more time to debug.
I would be addressing adding other SLAM and VIO examples first and get back to this.

Sure. Thank you.

Tried example from http://wiki.ros.org/rtabmap_ros/Tutorials/StereoHandHeldMapping with my OAK-D, and worked with latest rtabmap_ros version and also the ros-noetic-rtabmap-ros binaries on noetic. I tested with ros-noetic-depthai-ros binaries.
If it still don't work, things to check, after doing:
roslaunch depthai_examples stereo_inertial_node.launch depth_aligned:=false

rosrun imu_filter_madgwick imu_filter_node    \
   imu/data_raw:=/stereo_inertial_publisher/imu    \
   imu/data:=/stereo_inertial_publisher/imu/data     \
   _use_mag:=false    \
   _publish_tf:=false

do:
rostopic hz /stereo_inertial_publisher/left/image_rect \
   /stereo_inertial_publisher/right/image_rect \
   /stereo_inertial_publisher/left/camera_info \
   /stereo_inertial_publisher/right/camera_info \
   /stereo_inertial_publisher/imu/data

subscribed to [/stereo_inertial_publisher/left/image_rect]
subscribed to [/stereo_inertial_publisher/right/image_rect]
subscribed to [/stereo_inertial_publisher/left/camera_info]
subscribed to [/stereo_inertial_publisher/right/camera_info]
subscribed to [/stereo_inertial_publisher/imu/data]
                   topic                        rate   min_delta   max_delta   std_dev    window
================================================================================================
/stereo_inertial_publisher/left/image_rect     15.02   0.06438     0.06924     0.001187   14
/stereo_inertial_publisher/right/image_rect    14.95   0.06405     0.0708      0.002087   14
/stereo_inertial_publisher/left/camera_info    15.01   0.06357     0.06982     0.001641   15
/stereo_inertial_publisher/right/camera_info   14.98   0.06309     0.0711      0.002237   15
/stereo_inertial_publisher/imu/data            389.0   3.338e-06   0.0299      0.005644   14

Make sure topics are published! and a with a decent rate... though not sure why it is 15 Hz on my computer right now, but it still work.

Thanks @matlabbe

After the latest update published 3 days ago I still have ["oak_imu_frame" doesn't exist ] problem.
I have OAK-D-Pro and used launch file configuration mentioned above with ros2. Also, there is no data on /tf topic.
@matlabbe
`
ros2 run imu_filter_madgwick imu_filter_madgwick_node
--ros-args
-p use_mag:=false
-p publish_tf:=false
-p world_frame:="enu"
-r /imu/data_raw:=/imu
-r /imu/data:=/rtabmap/imu
ros2 launch rtabmap_ros
args:="--delete_db_on_start"
stereo:=true
left_image_topic:=/left/image_rect
right_image_topic:=/right/image_rect
left_camera_info_topic:=/left/camera_info
right_camera_info_topic:=/right/camera_info
imu_topic:=/rtabmap/imu
frame_id:=oak-d_frame
approx_sync:=true
approx_sync_max_interval:=0.001
wait_imu_to_init:=true
qos:=1
`
Terminal Output:
~/ros2_ws$ ros2 launch rtabmap_ros rtabmap.launch.py     args:="--delete_db_on_start"     stereo:=true     left_image_topic:=/left/image_rect     right_image_topic:=/right/image_rect     left_camera_info_topic:=/left/camera_info     right_camera_info_topic:=/right/camera_info     imu_topic:=/rtabmap/imu     frame_id:=oak-d-base-frame     approx_sync:=true     approx_sync_max_interval:=0.001     wait_imu_to_init:=true     qos:=1 [INFO] [launch]: All log files can be found below /home/droneai/.ros/log/2022-10-04-13-58-13-626687-asus-13024 [INFO] [launch]: Default logging verbosity is set to INFO [INFO] [stereo_odometry-1]: process started with pid [13026] [INFO] [rtabmap-2]: process started with pid [13028] [INFO] [rtabmapviz-3]: process started with pid [13030] [stereo_odometry-1] [INFO] [1664879293.885076717] [rtabmap.stereo_odometry]: Odometry: frame_id               = oak-d-base-frame [stereo_odometry-1] [INFO] [1664879293.885194067] [rtabmap.stereo_odometry]: Odometry: odom_frame_id          = odom [stereo_odometry-1] [INFO] [1664879293.885201672] [rtabmap.stereo_odometry]: Odometry: publish_tf             = true [stereo_odometry-1] [INFO] [1664879293.885207106] [rtabmap.stereo_odometry]: Odometry: wait_for_transform     = 0.200000 [stereo_odometry-1] [INFO] [1664879293.885235770] [rtabmap.stereo_odometry]: Odometry: initial_pose           = xyz=0.000000,0.000000,0.000000 rpy=0.000000,-0.000000,0.000000 [stereo_odometry-1] [INFO] [1664879293.885244131] [rtabmap.stereo_odometry]: Odometry: ground_truth_frame_id  =  [stereo_odometry-1] [INFO] [1664879293.885249428] [rtabmap.stereo_odometry]: Odometry: ground_truth_base_frame_id =  [stereo_odometry-1] [INFO] [1664879293.885254742] [rtabmap.stereo_odometry]: Odometry: config_path            =  [stereo_odometry-1] [INFO] [1664879293.885259748] [rtabmap.stereo_odometry]: Odometry: publish_null_when_lost = true [stereo_odometry-1] [INFO] [1664879293.885265408] [rtabmap.stereo_odometry]: Odometry: guess_frame_id         =  [stereo_odometry-1] [INFO] [1664879293.885270662] [rtabmap.stereo_odometry]: Odometry: guess_min_translation  = 0.000000 [stereo_odometry-1] [INFO] [1664879293.885276711] [rtabmap.stereo_odometry]: Odometry: guess_min_rotation     = 0.000000 [stereo_odometry-1] [INFO] [1664879293.885282624] [rtabmap.stereo_odometry]: Odometry: guess_min_time         = 0.000000 [stereo_odometry-1] [INFO] [1664879293.885288358] [rtabmap.stereo_odometry]: Odometry: expected_update_rate   = 0.000000 Hz [stereo_odometry-1] [INFO] [1664879293.885293994] [rtabmap.stereo_odometry]: Odometry: max_update_rate        = 0.000000 Hz [stereo_odometry-1] [INFO] [1664879293.885299670] [rtabmap.stereo_odometry]: Odometry: wait_imu_to_init       = true [stereo_odometry-1] [INFO] [1664879293.885362525] [rtabmap.stereo_odometry]: Odometry: stereoParams_=1 visParams_=1 icpParams_=0 [stereo_odometry-1] [INFO] [1664879293.937196272] [rtabmap.stereo_odometry]: odometry: Subscribing to IMU topic /rtabmap/imu [stereo_odometry-1] [INFO] [1664879293.937228380] [rtabmap.stereo_odometry]: odometry: qos_imu = 1 [stereo_odometry-1] [INFO] [1664879293.937541830] [rtabmap.stereo_odometry]: StereoOdometry: approx_sync = true [stereo_odometry-1] [INFO] [1664879293.937552094] [rtabmap.stereo_odometry]: StereoOdometry: approx_sync_max_interval = 0.001000 [stereo_odometry-1] [INFO] [1664879293.937561837] [rtabmap.stereo_odometry]: StereoOdometry: queue_size  = 10 [stereo_odometry-1] [INFO] [1664879293.937567412] [rtabmap.stereo_odometry]: RGBDOdometry: qos            = 1 [stereo_odometry-1] [INFO] [1664879293.937572840] [rtabmap.stereo_odometry]: RGBDOdometry: qos_camera_info = 1 [stereo_odometry-1] [INFO] [1664879293.937578047] [rtabmap.stereo_odometry]: StereoOdometry: subscribe_rgbd = false [stereo_odometry-1] [INFO] [1664879293.937583320] [rtabmap.stereo_odometry]: StereoOdometry: keep_color     = false [rtabmap-2] [INFO] [1664879293.941477349] [rtabmap.rtabmap]: rtabmap(maps): map_filter_radius          = 0.000000 [rtabmap-2] [INFO] [1664879293.941625047] [rtabmap.rtabmap]: rtabmap(maps): map_filter_angle           = 30.000000 [rtabmap-2] [INFO] [1664879293.941635578] [rtabmap.rtabmap]: rtabmap(maps): map_cleanup                = true [rtabmap-2] [INFO] [1664879293.941641730] [rtabmap.rtabmap]: rtabmap(maps): map_always_update          = false [rtabmap-2] [INFO] [1664879293.941646570] [rtabmap.rtabmap]: rtabmap(maps): map_empty_ray_tracing      = true [rtabmap-2] [INFO] [1664879293.941651735] [rtabmap.rtabmap]: rtabmap(maps): cloud_output_voxelized     = true [rtabmap-2] [INFO] [1664879293.941656551] [rtabmap.rtabmap]: rtabmap(maps): cloud_subtract_filtering   = false [rtabmap-2] [INFO] [1664879293.941661537] [rtabmap.rtabmap]: rtabmap(maps): cloud_subtract_filtering_min_neighbors = 2 [rtabmap-2] [INFO] [1664879293.941679390] [rtabmap.rtabmap]: rtabmap(maps): octomap_tree_depth         = 16 [stereo_odometry-1] [INFO] [1664879293.943443322] [rtabmap.stereo_odometry]:  [stereo_odometry-1] stereo_odometry subscribed to (approx sync, max interval=0.001000s): [stereo_odometry-1]    /left/image_rect \ [stereo_odometry-1]    /right/image_rect \ [stereo_odometry-1]    left/camera_info \ [stereo_odometry-1]    right/camera_info [rtabmap-2] [INFO] [1664879293.961076189] [rtabmap.rtabmap]: rtabmap: frame_id      = oak-d-base-frame [rtabmap-2] [INFO] [1664879293.961105877] [rtabmap.rtabmap]: rtabmap: map_frame_id  = map [rtabmap-2] [INFO] [1664879293.961111742] [rtabmap.rtabmap]: rtabmap: use_action_for_goal  = false [rtabmap-2] [INFO] [1664879293.961117417] [rtabmap.rtabmap]: rtabmap: tf_delay      = 0.050000 [rtabmap-2] [INFO] [1664879293.961128813] [rtabmap.rtabmap]: rtabmap: tf_tolerance  = 0.100000 [rtabmap-2] [INFO] [1664879293.961134541] [rtabmap.rtabmap]: rtabmap: odom_sensor_sync   = false [rtabmap-2] [INFO] [1664879293.961140546] [rtabmap.rtabmap]: rtabmap: stereo_to_depth = false [rtabmap-2] [INFO] [1664879293.961145390] [rtabmap.rtabmap]: rtabmap: gen_scan  = false [rtabmap-2] [INFO] [1664879293.961150275] [rtabmap.rtabmap]: rtabmap: gen_depth  = false [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [rtabmapviz-3] [INFO] [1664879294.010665668] [rtabmap.rtabmapviz]: rtabmapviz: Using configuration from "/home/droneai/.ros/rtabmapGUI.ini" [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [rtabmap-2] [INFO] [1664879294.087304821] [rtabmap.rtabmap]: RTAB-Map detection rate = 1.000000 Hz [rtabmap-2] [INFO] [1664879294.087456582] [rtabmap.rtabmap]: rtabmap: Deleted database "/home/droneai/.ros/rtabmap.db" (--delete_db_on_start or -d are set). [rtabmap-2] [INFO] [1664879294.087472717] [rtabmap.rtabmap]: rtabmap: Using database from "/home/droneai/.ros/rtabmap.db" (0 MB). [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [stereo_odometry-1] Warning: Invalid frame ID "oak_imu_frame" passed to canTransform argument source_frame - frame does not exist [stereo_odometry-1]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.13/src/buffer_core.cpp [rtabmap-2] [INFO] [1664879294.144278104] [rtabmap.rtabmap]: rtabmap: Database version = "0.20.21".

I guess you are referring to this example: https://github.com/introlab/rtabmap/issues/742#issuecomment-1259965385
Got an issue (not the one you have) explained in the following post but it is now fixed in latest master branch rtabmap_ros 0.20.20 (will soon be released as binaries). Overall, I didn't see your issue. Can you tell us the exact version of depthai-ros used?

You could launch with wait_imu_to_init:=true to ignore imu. I don't have an Oak-D Pro, but if there is an imu topic, maybe the corresponding TF is not correctly published by depthai node. What is the TF tree?
ros2 run tf2_tools view_frames

Here is mine with normal Oak-D:

Actually, I believe this is the problem. I don't have oak_imu_frame. I also think this is why I cannot run Rtabmap. Also, I asked a friend to test OAK-D-S2; the result was the same as the picture below.

And thanks for your reply.

Update:
I use camera_model:=OAK-D instead of camera_model:=OAK-D-PRO and then I have oak_imu_frame.
'''
ros2 launch depthai_examples stereo_inertial_node.launch.py camera_model:=OAK-D
'''

I am still having some issues in ros1 with the oak-d camera. This happened after i decided to build rtabmap with DEPTHAI_CORE=ON, i also have two opencv version 4.0 and 3.4.9. I had to install 4.0 becaue depth core ai needed it. is the issue related to the opencv versions ?
ros : melodic
please help @matlabbe
roslaunch rtabmap_ros rtabmap.launch args:="--delete_db_on_start" \
> rgb_topic:=/stereo_inertial_publisher/color/image \
> camera_info_topic:=/stereo_inertial_publisher/color/camera_info \
> depth_topic:=/stereo_inertial_publisher/stereo/depth \
> imu_topic:=/stereo_inertial_publisher/imu \
> frame_id:=oak-d_frame \
> approx_sync:=true \
> approx_sync_max_interval:=0.001 \
> wait_imu_to_init:=true

... logging to /home/ubuntu/.ros/log/d8584b62-48e9-11ed-a7ff-bf1d1f317710/roslaunch-ubuntu-3271.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://<IP_ADDRESS>:33355/

SUMMARY
========

CLEAR PARAMETERS
 * /rtabmap/rgbd_odometry/
 * /rtabmap/rtabmap/
 * /rtabmap/rtabmapviz/

PARAMETERS
 * /rosdistro: melodic
 * /rosversion: 1.14.13
 * /rtabmap/rgbd_odometry/approx_sync: True
 * /rtabmap/rgbd_odometry/approx_sync_max_interval: 0.001
 * /rtabmap/rgbd_odometry/config_path:
 * /rtabmap/rgbd_odometry/expected_update_rate: 0.0
 * /rtabmap/rgbd_odometry/frame_id: oak-d_frame
 * /rtabmap/rgbd_odometry/ground_truth_base_frame_id:
 * /rtabmap/rgbd_odometry/ground_truth_frame_id:
 * /rtabmap/rgbd_odometry/guess_frame_id:
 * /rtabmap/rgbd_odometry/guess_min_rotation: 0.0
 * /rtabmap/rgbd_odometry/guess_min_translation: 0.0
 * /rtabmap/rgbd_odometry/keep_color: False
 * /rtabmap/rgbd_odometry/max_update_rate: 0.0
 * /rtabmap/rgbd_odometry/odom_frame_id: odom
 * /rtabmap/rgbd_odometry/publish_tf: True
 * /rtabmap/rgbd_odometry/queue_size: 10
 * /rtabmap/rgbd_odometry/subscribe_rgbd: False
 * /rtabmap/rgbd_odometry/wait_for_transform_duration: 0.2
 * /rtabmap/rgbd_odometry/wait_imu_to_init: True
 * /rtabmap/rtabmap/Mem/IncrementalMemory: true
 * /rtabmap/rtabmap/Mem/InitWMWithAllNodes: false
 * /rtabmap/rtabmap/approx_sync: True
 * /rtabmap/rtabmap/config_path:
 * /rtabmap/rtabmap/database_path: ~/.ros/rtabmap.db
 * /rtabmap/rtabmap/frame_id: oak-d_frame
 * /rtabmap/rtabmap/gen_depth: False
 * /rtabmap/rtabmap/gen_depth_decimation: 1
 * /rtabmap/rtabmap/gen_depth_fill_holes_error: 0.1
 * /rtabmap/rtabmap/gen_depth_fill_holes_size: 0
 * /rtabmap/rtabmap/gen_depth_fill_iterations: 1
 * /rtabmap/rtabmap/gen_scan: False
 * /rtabmap/rtabmap/ground_truth_base_frame_id:
 * /rtabmap/rtabmap/ground_truth_frame_id:
 * /rtabmap/rtabmap/landmark_angular_variance: 9999.0
 * /rtabmap/rtabmap/landmark_linear_variance: 0.0001
 * /rtabmap/rtabmap/map_frame_id: map
 * /rtabmap/rtabmap/odom_frame_id:
 * /rtabmap/rtabmap/odom_frame_id_init:
 * /rtabmap/rtabmap/odom_sensor_sync: False
 * /rtabmap/rtabmap/odom_tf_angular_variance: 0.001
 * /rtabmap/rtabmap/odom_tf_linear_variance: 0.001
 * /rtabmap/rtabmap/publish_tf: True
 * /rtabmap/rtabmap/queue_size: 10
 * /rtabmap/rtabmap/scan_cloud_max_points: 0
 * /rtabmap/rtabmap/subscribe_depth: True
 * /rtabmap/rtabmap/subscribe_odom_info: True
 * /rtabmap/rtabmap/subscribe_rgb: True
 * /rtabmap/rtabmap/subscribe_rgbd: False
 * /rtabmap/rtabmap/subscribe_scan: False
 * /rtabmap/rtabmap/subscribe_scan_cloud: False
 * /rtabmap/rtabmap/subscribe_scan_descriptor: False
 * /rtabmap/rtabmap/subscribe_stereo: False
 * /rtabmap/rtabmap/subscribe_user_data: False
 * /rtabmap/rtabmap/wait_for_transform_duration: 0.2
 * /rtabmap/rtabmapviz/approx_sync: True
 * /rtabmap/rtabmapviz/frame_id: oak-d_frame
 * /rtabmap/rtabmapviz/odom_frame_id:
 * /rtabmap/rtabmapviz/queue_size: 10
 * /rtabmap/rtabmapviz/subscribe_depth: True
 * /rtabmap/rtabmapviz/subscribe_odom_info: True
 * /rtabmap/rtabmapviz/subscribe_rgb: True
 * /rtabmap/rtabmapviz/subscribe_rgbd: False
 * /rtabmap/rtabmapviz/subscribe_scan: False
 * /rtabmap/rtabmapviz/subscribe_scan_cloud: False
 * /rtabmap/rtabmapviz/subscribe_scan_descriptor: False
 * /rtabmap/rtabmapviz/subscribe_stereo: False
 * /rtabmap/rtabmapviz/wait_for_transform_duration: 0.2

NODES
  /rtabmap/
    rgbd_odometry (rtabmap_ros/rgbd_odometry)
    rtabmap (rtabmap_ros/rtabmap)
    rtabmapviz (rtabmap_ros/rtabmapviz)

ROS_MASTER_URI=http://<IP_ADDRESS>:11311

process[rtabmap/rgbd_odometry-1]: started with pid [3287]
process[rtabmap/rtabmap-2]: started with pid [3288]
process[rtabmap/rtabmapviz-3]: started with pid [3289]
[ INFO] [1665440550.962715920]: Starting node...
[ INFO] [1665440551.022443516]: Initializing nodelet with 4 worker threads.
[ INFO] [1665440551.286785917]: Initializing nodelet with 4 worker threads.
[ INFO] [1665440551.525815216]: Odometry: frame_id               = oak-d_frame
[ INFO] [1665440551.526057612]: Odometry: odom_frame_id          = odom
[ INFO] [1665440551.526202369]: Odometry: publish_tf             = true
[ INFO] [1665440551.526310385]: Odometry: wait_for_transform     = true
[ INFO] [1665440551.526419753]: Odometry: wait_for_transform_duration  = 0.200000
[ INFO] [1665440551.526664447]: Odometry: initial_pose           = xyz=0.000000,0.000000,0.000000 rpy=0.000000,-0.000000,0.000000
[ INFO] [1665440551.526806146]: Odometry: ground_truth_frame_id  =
[ INFO] [1665440551.526919035]: Odometry: ground_truth_base_frame_id =
[ INFO] [1665440551.526998815]: Odometry: config_path            =
[ INFO] [1665440551.527105812]: Odometry: publish_null_when_lost = true
[ INFO] [1665440551.527191261]: Odometry: guess_frame_id         =
[ INFO] [1665440551.527285770]: Odometry: guess_min_translation  = 0.000000
[ INFO] [1665440551.527414222]: Odometry: guess_min_rotation     = 0.000000
[ INFO] [1665440551.527520589]: Odometry: guess_min_time         = 0.000000
[ INFO] [1665440551.527618804]: Odometry: expected_update_rate   = 0.000000 Hz
[ INFO] [1665440551.527706588]: Odometry: max_update_rate        = 0.000000 Hz
[ INFO] [1665440551.527812047]: Odometry: wait_imu_to_init       = true
[ INFO] [1665440551.527977258]: Odometry: stereoParams_=0 visParams_=1 icpParams_=0
[ INFO] [1665440551.750051312]: Starting node...
libEGL warning: DRI2: failed to authenticate
[ INFO] [1665440552.330830975]: /rtabmap/rtabmap(maps): map_filter_radius          = 0.000000
[ INFO] [1665440552.331943525]: /rtabmap/rtabmap(maps): map_filter_angle           = 30.000000
[ INFO] [1665440552.332767807]: /rtabmap/rtabmap(maps): map_cleanup                = true
[ INFO] [1665440552.333706199]: /rtabmap/rtabmap(maps): map_always_update          = false
[ INFO] [1665440552.334363884]: /rtabmap/rtabmap(maps): map_empty_ray_tracing      = true
[ INFO] [1665440552.334853099]: /rtabmap/rtabmap(maps): cloud_output_voxelized     = true
[ INFO] [1665440552.335283878]: /rtabmap/rtabmap(maps): cloud_subtract_filtering   = false
[ INFO] [1665440552.335678808]: /rtabmap/rtabmap(maps): cloud_subtract_filtering_min_neighbors = 2
[ INFO] [1665440552.662171186]: rtabmap: frame_id      = oak-d_frame
[ INFO] [1665440552.662400777]: rtabmap: map_frame_id  = map
[ INFO] [1665440552.664508801]: rtabmap: use_action_for_goal  = false
[ INFO] [1665440552.666329893]: rtabmap: tf_delay      = 0.050000
[ INFO] [1665440552.669632932]: rtabmap: tf_tolerance  = 0.100000
[ INFO] [1665440552.671023892]: rtabmap: odom_sensor_sync   = false
[ INFO] [1665440552.679360334]: rtabmap: gen_scan  = false
[ INFO] [1665440552.679728510]: rtabmap: gen_depth  = false
[ INFO] [1665440553.240082000]: rtabmapviz: Using configuration from "/home/ubuntu/.ros/rtabmap_gui.ini"
[ INFO] [1665440554.479714673]: Setting RTAB-Map parameter "Mem/IncrementalMemory"="true"
[ INFO] [1665440554.483003418]: Setting RTAB-Map parameter "Mem/InitWMWithAllNodes"="false"
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[ INFO] [1665440555.961264972]: odometry: Subscribing to IMU topic /stereo_inertial_publisher/imu
[ INFO] [1665440556.024469508]: RGBDOdometry: approx_sync    = true
[ INFO] [1665440556.024677505]: RGBDOdometry: approx_sync_max_interval = 0.001000
[ INFO] [1665440556.025314741]: RGBDOdometry: queue_size     = 10
[ INFO] [1665440556.025997236]: RGBDOdometry: subscribe_rgbd = false
[ INFO] [1665440556.026490225]: RGBDOdometry: rgbd_cameras   = 1
[ INFO] [1665440556.026895084]: RGBDOdometry: keep_color     = false
[ INFO] [1665440556.165364522]:
/rtabmap/rgbd_odometry subscribed to (approx sync, max interval=0.001000s):
   /stereo_inertial_publisher/color/image \
   /stereo_inertial_publisher/stereo/depth \
   /stereo_inertial_publisher/color/camera_info
[ INFO] [1665440557.401614014]: rtabmapviz: Reading parameters from the ROS server...
[ INFO] [1665440557.405905006]: rtabmapviz: Cannot get rtabmap's parameters, waiting max 5 seconds in case the node has just been launched.
[ERROR] [1665440557.513437536]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440555.854913 and new one is<PHONE_NUMBER>.054833, last imu stamp received=1665440555.195768)
[ERROR] [1665440557.604228812]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440556.054833 and new one is<PHONE_NUMBER>.121438, last imu stamp received=1665440555.251172)
[ERROR] [1665440557.790638673]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440556.121438 and new one is<PHONE_NUMBER>.321357, last imu stamp received=1665440555.391233)
[ERROR] [1665440557.896704555]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440556.321357 and new one is<PHONE_NUMBER>.454618, last imu stamp received=1665440555.566531)
[ERROR] [1665440558.050272526]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440556.454618 and new one is<PHONE_NUMBER>.587881, last imu stamp received=1665440555.752129)
[ERROR] [1665440558.103347188]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440556.587881 and new one is<PHONE_NUMBER>.721142, last imu stamp received=1665440555.846802)
[ERROR] [1665440558.200140474]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440556.721142 and new one is<PHONE_NUMBER>.787751, last imu stamp received=1665440555.902015)
[ERROR] [1665440558.280270704]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440556.787751 and new one is<PHONE_NUMBER>.920994, last imu stamp received=1665440555.949122)
[ERROR] [1665440558.559173389]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440556.920994 and new one is<PHONE_NUMBER>.187518, last imu stamp received=1665440556.272772)
[ INFO] [1665440558.569212295]: RTAB-Map detection rate = 1.000000 Hz
[ INFO] [1665440558.572651264]: rtabmap: Deleted database "/home/ubuntu/.ros/rtabmap.db" (--delete_db_on_start or -d are set).
[ INFO] [1665440558.573409628]: rtabmap: Using database from "/home/ubuntu/.ros/rtabmap.db" (0 MB).
[ERROR] [1665440558.661990990]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440557.187518 and new one is<PHONE_NUMBER>.254175, last imu stamp received=1665440556.408976)
[ERROR] [1665440558.745007558]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440557.254175 and new one is<PHONE_NUMBER>.387439, last imu stamp received=1665440556.459840)
[ERROR] [1665440558.963828201]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440557.387439 and new one is<PHONE_NUMBER>.587303, last imu stamp received=1665440556.791345)
[ERROR] [1665440559.061845932]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440557.587303 and new one is<PHONE_NUMBER>.653961, last imu stamp received=1665440556.842659)
[ INFO] [1665440559.079750542]: rtabmap: Database version = "0.20.21".
[ INFO] [1665440559.079922276]: rtabmap: SLAM mode (Mem/IncrementalMemory=true)
[ERROR] [1665440559.234142642]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440557.653961 and new one is<PHONE_NUMBER>.853844, last imu stamp received=1665440557.065539)
[ INFO] [1665440559.307269252]: /rtabmap/rtabmap: subscribe_depth = true
[ INFO] [1665440559.307526390]: /rtabmap/rtabmap: subscribe_rgb = true
[ INFO] [1665440559.307626838]: /rtabmap/rtabmap: subscribe_stereo = false
[ INFO] [1665440559.307713409]: /rtabmap/rtabmap: subscribe_rgbd = false (rgbd_cameras=1)
[ INFO] [1665440559.307823026]: /rtabmap/rtabmap: subscribe_odom_info = true
[ INFO] [1665440559.307907819]: /rtabmap/rtabmap: subscribe_user_data = false
[ INFO] [1665440559.307987702]: /rtabmap/rtabmap: subscribe_scan = false
[ INFO] [1665440559.308072088]: /rtabmap/rtabmap: subscribe_scan_cloud = false
[ INFO] [1665440559.308147321]: /rtabmap/rtabmap: subscribe_scan_descriptor = false
[ INFO] [1665440559.308240080]: /rtabmap/rtabmap: queue_size    = 10
[ INFO] [1665440559.308324687]: /rtabmap/rtabmap: approx_sync   = true
[ INFO] [1665440559.308761063]: Setup depth callback
[ERROR] [1665440559.438515265]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440557.853844 and new one is<PHONE_NUMBER>.987097, last imu stamp received=1665440557.306073)
[ INFO] [1665440559.478649545]:
/rtabmap/rtabmap subscribed to (approx sync):
   /rtabmap/odom \
   /stereo_inertial_publisher/color/image \
   /stereo_inertial_publisher/stereo/depth \
   /stereo_inertial_publisher/color/camera_info \
   /rtabmap/odom_info
[ERROR] [1665440559.613444367]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440557.987097 and new one is<PHONE_NUMBER>.253607, last imu stamp received=1665440557.558669)
[ERROR] [1665440559.926143022]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440558.253607 and new one is<PHONE_NUMBER>.453525, last imu stamp received=1665440557.678922)
[ERROR] [1665440559.983743739]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440558.453525 and new one is<PHONE_NUMBER>.520129, last imu stamp received=1665440557.795286)
[ERROR] [1665440560.114339660]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440558.520129 and new one is<PHONE_NUMBER>.720049, last imu stamp received=1665440557.984522)
[ERROR] [1665440560.321532368]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440558.720049 and new one is<PHONE_NUMBER>.919915, last imu stamp received=1665440558.130447)
[ERROR] [1665440560.411310350]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440558.919915 and new one is<PHONE_NUMBER>.053177, last imu stamp received=1665440558.227239)
[ERROR] [1665440560.471533018]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440559.053177 and new one is<PHONE_NUMBER>.119834, last imu stamp received=1665440558.376880)
[ERROR] [1665440560.671133119]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440559.119834 and new one is<PHONE_NUMBER>.253098, last imu stamp received=1665440558.615530)
[ERROR] [1665440560.733913290]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440559.253098 and new one is<PHONE_NUMBER>.319701, last imu stamp received=1665440558.712334)
[ERROR] [1665440560.840897965]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440559.319701 and new one is<PHONE_NUMBER>.446397, last imu stamp received=1665440558.915528)
[ERROR] [1665440560.895689118]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440559.446397 and new one is<PHONE_NUMBER>.513054, last imu stamp received=1665440559.013941)
[ERROR] [1665440561.100798583]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440559.513054 and new one is<PHONE_NUMBER>.646316, last imu stamp received=1665440559.369120)
[ERROR] [1665440561.143372202]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440559.646316 and new one is<PHONE_NUMBER>.779593, last imu stamp received=1665440559.411828)
[ERROR] [1665440561.263514534]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440559.779593 and new one is<PHONE_NUMBER>.846198, last imu stamp received=1665440559.555639)
[ERROR] [1665440561.348412660]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440559.846198 and new one is<PHONE_NUMBER>.979453, last imu stamp received=1665440559.604931)
[ERROR] [1665440561.488486071]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440559.979453 and new one is<PHONE_NUMBER>.046109, last imu stamp received=1665440559.742971)
[ERROR] [1665440561.567953033]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440560.046109 and new one is<PHONE_NUMBER>.179364, last imu stamp received=1665440559.938503)
[ERROR] [1665440561.638914752]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440560.179364 and new one is<PHONE_NUMBER>.245961, last imu stamp received=1665440560.015115)
[ERROR] [1665440561.854034486]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440560.245961 and new one is<PHONE_NUMBER>.445884, last imu stamp received=1665440560.192806)
[ERROR] [1665440562.058368477]: Overwriting previous data! Make sure IMU is published faster than data rate. (last image stamp buffered=1665440560.445884 and new one is<PHONE_NUMBER>.645747, last imu stamp received=1665440560.439069)
[ WARN] [1665440562.477007709]: rtabmapviz: rtabmap's parameters seem not all there yet! continuing with those there if some...
[ INFO] [1665440562.747541363]: rtabmap 0.20.21 started...
[rtabmap/rgbd_odometry-1] process has died [pid 3287, exit code -7, cmd /home/ubuntu/catkin_ws/devel/lib/rtabmap_ros/rgbd_odometry --delete_db_on_start rgb/image:=/stereo_inertial_publisher/color/image depth/image:=/stereo_inertial_publisher/stereo/depth rgb/camera_info:=/stereo_inertial_publisher/color/camera_info rgbd_image:=rgbd_image_relay odom:=odom imu:=/stereo_inertial_publisher/imu __name:=rgbd_odometry __log:=/home/ubuntu/.ros/log/d8584b62-48e9-11ed-a7ff-bf1d1f317710/rtabmap-rgbd_odometry-1.log].
log file: /home/ubuntu/.ros/log/d8584b62-48e9-11ed-a7ff-bf1d1f317710/rtabmap-rgbd_odometry-1*.log
[ INFO] [1665440564.109295783]: rtabmapviz: Parameters read = 358
[ INFO] [1665440564.109452559]: rtabmapviz: Parameters successfully read.
[ WARN] [1665440564.481725301]: /rtabmap/rtabmap: Did not receive data since 5 seconds! Make sure the input topics are published ("$ rostopic hz my_topic") and the timestamps in their header are set. If topics are coming from different computers, make sure the clocks of the computers are synchronized ("ntpdate"). If topics are not published at the same rate, you could increase "queue_size" parameter (current=10).
/rtabmap/rtabmap subscribed to (approx sync):
   /rtabmap/odom \
   /stereo_inertial_publisher/color/image \
   /stereo_inertial_publisher/stereo/depth \
   /stereo_inertial_publisher/color/camera_info \
   /rtabmap/odom_info
[ INFO] [1665440565.654747166]: /rtabmap/rtabmapviz: subscribe_depth = true
[ INFO] [1665440565.654875506]: /rtabmap/rtabmapviz: subscribe_rgb = true
[ INFO] [1665440565.654941176]: /rtabmap/rtabmapviz: subscribe_stereo = false
[ INFO] [1665440565.655008569]: /rtabmap/rtabmapviz: subscribe_rgbd = false (rgbd_cameras=1)
[ INFO] [1665440565.655092690]: /rtabmap/rtabmapviz: subscribe_odom_info = true
[ INFO] [1665440565.655149913]: /rtabmap/rtabmapviz: subscribe_user_data = false
[ INFO] [1665440565.655201875]: /rtabmap/rtabmapviz: subscribe_scan = false
[ INFO] [1665440565.655250781]: /rtabmap/rtabmapviz: subscribe_scan_cloud = false
[ INFO] [1665440565.655299760]: /rtabmap/rtabmapviz: subscribe_scan_descriptor = false
[ INFO] [1665440565.655348666]: /rtabmap/rtabmapviz: queue_size    = 10
[ INFO] [1665440565.655399849]: /rtabmap/rtabmapviz: approx_sync   = true
[ INFO] [1665440565.655480303]: Setup depth callback
[ INFO] [1665440565.982640529]:
/rtabmap/rtabmapviz subscribed to (approx sync):
   /rtabmap/odom \
   /stereo_inertial_publisher/color/image \
   /stereo_inertial_publisher/stereo/depth \
   /stereo_inertial_publisher/color/camera_info \
   /rtabmap/odom_info
[ INFO] [1665440565.983081233]: rtabmapviz started.
[ WARN] [1665440569.482108982]: /rtabmap/rtabmap: Did not receive data since 5 seconds! Make sure the input topics are published ("$ rostopic hz my_topic") and the timestamps in their header are set. If topics are coming from different computers, make sure the clocks of the computers are synchronized ("ntpdate"). If topics are not published at the same rate, you could increase "queue_size" parameter (current=10).
/rtabmap/rtabmap subscribed to (approx sync):
   /rtabmap/odom \
   /stereo_inertial_publisher/color/image \
   /stereo_inertial_publisher/stereo/depth \
   /stereo_inertial_publisher/color/camera_info \
   /rtabmap/odom_info
[ WARN] [1665440570.983203588]: /rtabmap/rtabmapviz: Did not receive data since 5 seconds! Make sure the input topics are published ("$ rostopic hz my_topic") and the timestamps in their header are set. If topics are coming from different computers, make sure the clocks of the computers are synchronized ("ntpdate"). If topics are not published at the same rate, you could increase "queue_size" parameter (current=10).
/rtabmap/rtabmapviz subscribed to (approx sync):
   /rtabmap/odom \
   /stereo_inertial_publisher/color/image \
   /stereo_inertial_publisher/stereo/depth \
   /stereo_inertial_publisher/color/camera_info \
   /rtabmap/odom_info
[ WARN] [1665440574.482546037]: /rtabmap/rtabmap: Did not receive data since 5 seconds! Make sure the input topics are published ("$ rostopic hz my_topic") and the timestamps in their header are set. If topics are coming from different computers, make sure the clocks of the computers are synchronized ("ntpdate"). If topics are not published at the same rate, you could increase "queue_size" parameter (current=10).
/rtabmap/rtabmap subscribed to (approx sync):
   /rtabmap/odom \
   /stereo_inertial_publisher/color/image \
   /stereo_inertial_publisher/stereo/depth \
   /stereo_inertial_publisher/color/camera_info \
   /rtabmap/odom_info
[ WARN] [1665440575.984063855]: /rtabmap/rtabmapviz: Did not receive data since 5 seconds! Make sure the input topics are published ("$ rostopic hz my_topic") and the timestamps in their header are set. If topics are coming from different computers, make sure the clocks of the computers are synchronized ("ntpdate"). If topics are not published at the same rate, you could increase "queue_size" parameter (current=10).
/rtabmap/rtabmapviz subscribed to (approx sync):
   /rtabmap/odom \
   /stereo_inertial_publisher/color/image \
   /stereo_inertial_publisher/stereo/depth \
   /stereo_inertial_publisher/color/camera_info \
   /rtabmap/odom_info
[ WARN] [1665440579.483918138]: /rtabmap/rtabmap: Did not receive data since 5 seconds! Make sure the input topics are published ("$ rostopic hz my_topic") and the timestamps in their header are set. If topics are coming from different computers, make sure the clocks of the computers are synchronized ("ntpdate"). If topics are not published at the same rate, you could increase "queue_size" parameter (current=10).
/rtabmap/rtabmap subscribed to (approx sync):
   /rtabmap/odom \
   /stereo_inertial_publisher/color/image \
   /stereo_inertial_publisher/stereo/depth \
   /stereo_inertial_publisher/color/camera_info \
   /rtabmap/odom_info
[ WARN] [1665440580.985067224]: /rtabmap/rtabmapviz: Did not receive data since 5 seconds! Make sure the input topics are published ("$ rostopic hz my_topic") and the timestamps in their header are set. If topics are coming from different computers, make sure the clocks of the computers are synchronized ("ntpdate"). If topics are not published at the same rate, you could increase "queue_size" parameter (current=10).
/rtabmap/rtabmapviz subscribed to (approx sync):
   /rtabmap/odom \
   /stereo_inertial_publisher/color/image \
   /stereo_inertial_publisher/stereo/depth \
   /stereo_inertial_publisher/color/camera_info \
   /rtabmap/odom_info
roslaunch rtabmap_ros rtabmap.launch args:="--delete_db_on_start" \
rgb_topic:=/stereo_inertial_publisher/color/image \
camera_info_topic:=/stereo_inertial_publisher/color/camera_info \
depth_topic:=/stereo_inertial_publisher/stereo/depth \
imu_topic:=/stereo_inertial_publisher/imu \
frame_id:=oak-d_frame \
approx_sync:=true \
approx_sync_max_interval:=0.001 \
wait_imu_to_init:=true
[ WARN] [1665440584.484688980]: /rtabmap/rtabmap: Did not receive data since 5 seconds! Make sure the input topics are published ("$ rostopic hz my_topic") and the timestamps in their header are set. If topics are coming from different computers, make sure the clocks of the computers are synchronized ("ntpdate"). If topics are not published at the same rate, you could increase "queue_size" parameter (current=10).
/rtabmap/rtabmap subscribed to (approx sync):
   /rtabmap/odom \
   /stereo_inertial_publisher/color/image \
   /stereo_inertial_publisher/stereo/depth \
   /stereo_inertial_publisher/color/camera_info \
   /rtabmap/odom_info
[ WARN] [1665440585.985665026]: /rtabmap/rtabmapviz: Did not receive data since 5 seconds! Make sure the input topics are published ("$ rostopic hz my_topic") and the timestamps in their header are set. If topics are coming from different computers, make sure the clocks of the computers are synchronized ("ntpdate"). If topics are not published at the same rate, you could increase "queue_size" parameter (current=10).
/rtabmap/rtabmapviz subscribed to (approx sync):
   /rtabmap/odom \
   /stereo_inertial_publisher/color/image \
   /stereo_inertial_publisher/stereo/depth \
   /stereo_inertial_publisher/color/camera_info \
   /rtabmap/odom_info
^C[rtabmap/rtabmapviz-3] killing on exit
[ INFO] [1665440587.865340018]: rtabmapviz: ctrl-c catched! Exiting Qt app...
[rtabmap/rtabmap-2] killing on exit
rtabmap: Saving database/long-term memory... (located at /home/ubuntu/.ros/rtabmap.db)
rtabmap: Saving database/long-term memory...done! (located at /home/ubuntu/.ros/rtabmap.db, 0 MB)

i rebuilt rtbamap without depthai_core and still got the error mentioned above. Does rtabmap support opencv version higher than 3.2.I did get warnings of potential conflicts of version @matlabbe
thank you for your help

@an99990 If you mix up many opencv versions on your computer, it is likely that it may cause some crashes in libraries/apps using opencv. To use latest OpenCV version, you will have to unsintall opencv binaries from your computer. This will uninstall cv_bridge package and all packages depending on it, so you would have to rebuild all those packages from source so that they all link on that opencv version. To use opencv modules that are not installed with the binaries, a workaround is to rebuild the same opencv version than the binaries on your platform (see comment here about rebuilding opencv).


crash when using aws-lambda instrumentation

I've been running into an exception where the JS auto-instrumentation attempts to load package.json from the base path of a lambda handler. Is there a way to customize the path from /var/task/src/handlers/my-function-name/package.json to a higher level /var/task/package.json or /opt/my-extension/package.json?
Copying the package.json into the expected locations causes the instrumentation to work as expected, it would just be painful for the project's build process.
Setup:

AWS managed Lambda Layer for ADOT JavaScript SDK and ADOT Collector
OpenTelemetry JS v0.18.0
OpenTelemetry JS Contrib v0.20b0,
ADOT Collector for Lambda v0.9.1
Node 12 runtimes
Serverless framework builds and deploys

Exception:
2021-05-07T16:40:57.227Z undefined ERROR Uncaught Exception {"errorType":"Runtime.ImportModuleError",
"errorMessage":"Error: Cannot find module '/var/task/src/handlers/my-function-name/package.json'\n
Require stack:\n-<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS> /opt/wrapper.js\n-

 internal/preload","stack":["Runtime.ImportModuleError: Error: Cannot find module '/var/task/src/handlers/my-function-name/package.json'",
 "Require stack:","- /opt/nodejs/node_modules/@opentelemetry/instrumentation/build/src/platform/node/instrumentation.js","-
  /opt/nodejs/node_modules/@opentelemetry/instrumentation/build/src/platform/node/index.js","-
   /opt/nodejs/node_modules/@opentelemetry/instrumentation/build/src/platform/index.js","-
    /opt/nodejs/node_modules/@opentelemetry/instrumentation/build/src/autoLoader.js","-
     /opt/nodejs/node_modules/@opentelemetry/instrumentation/build/src/index.js","-
      /opt/nodejs/node_modules/@opentelemetry/instrumentation-aws-lambda/build/src/aws-lambda.js","-
       /opt/nodejs/node_modules/@opentelemetry/instrumentation-aws-lambda/build/src/index.js","-
        /opt/wrapper.js","- internal/preload"," at _loadUserApp (/var/runtime/UserFunction.js:100:13)","
         at Object.module.exports.load (/var/runtime/UserFunction.js:140:17)"," at Object.<anonymous> (/var/runtime/index.js:43:30)",
         " at Module._compile (internal/modules/cjs/loader.js:999:30)","
         at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)"," at Module.load (internal/modules/cjs/loader.js:863:32)","
          at Function.Module._load (internal/modules/cjs/loader.js:708:14)","
           at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)"," at internal/main/run_main_module.js:17:47"]}

Originally posted by @adambartholomew in https://github.com/open-telemetry/opentelemetry-js/discussions/2192

Thanks for bringing this up, here's the problematic require in the base instrumentation: https://github.com/open-telemetry/opentelemetry-js/blob/1758fa6e84333c9c43cc468c5e99dd3646f7e3c7/packages/opentelemetry-instrumentation/src/platform/node/instrumentation.ts#L76
One suggestion is we could use pkginfo which is made for this use case. All it does is recursively search up the file tree for the first package.json it finds, so we could also roll our own solution for that if we wanted to avoid the dependency.

I would prefer to have this logic in the base instrumentation to avoid the dependency indeed (specially since we only need this code for the node platform)

I believe this is happening because lambda have a require path behavior than node itself, i'm converting this into an issue since its a bug in the base instrumentation class
/cc @anuraaga @willarmiros

I don't believe that amazon has a different require behavior. They do change some of the require path configuration, but I believe the resolution behavior is still the documented node behavior.

When is this bug triggered? I assume not for all lambda invocations, so does it only happen when the user application doesn't have a package.json? Which module is being intercepted that uses the user's application as the base path? Is it the load of the user application itself?

I assume not for all lambda invocations, so does it only happen when the user application doesn't have a package.json?

Based on @adambartholomew's original issue, it sounds like there was a package.json at the root of the function bundle (at /var/task), but this error still occurred because it was searching in the baseDir /var/task/src/handlers/my-function-name.
One thing I'm unclear on is what exactly require-in-the-middle is intended to be used for. My understanding is it's a way to safely require modules that are targeted for instrumentation so that we can execute instrumentation logic when the module is being imported. This would make me think that the baseDir (on the line I linked above) would always be pointing to the customer's app rather than the instrumented module as expected. Could someone help clarify that?

require-in-the-middle intercepts the require of instrumented modules. For instance the mysql instrumentation registers a RITM hook for the mysql module. When the customer app calls require('mysql'), our hook is fired before the require returns the module to the user app. In this hook we patch anything we need. The basedir is typically the directory of the instrumented module (in this case mysql) so we can check to ensure it is a version we are capable of instrumenting.

Ok that makes sense. I think the root issue here is that the Lambda instrumentation follows a different pattern for declaring its target module instrumentation. Typically, instrumented modules are well-defined module names (e.g. mysql) that are the same as the name of their NPM package and have a package.json available at the root by definition. The Lambda instrumentation is targeting an arbitrary user-defined module instead, wherever their Lambda request handler happens to be. This weirdness was briefly discussed in review.
The problem now is that package.json does not necessarily exist alongside the handler (as was the case here), or at all, in a Lambda function. So I propose a few options:

Stick with the recursive search in #2206, since it will be the same as existing behavior for all "normal" modules where the package.json is right where you'd expect it and no recursion is needed.
Given that the Lambda instrumentation accepts all versions, we could just skip the package.json require & check altogether if all versions are accepted, as a special case.
Similar to option 2. Change the InstrumentationNodeModuleDefinition to have supported versions as optional, since it's clearly not applicable for this instrumentation, and skip the version checks if not provided.

I'm pretty sure (3) is already the case.

I think it's required? https://github.com/open-telemetry/opentelemetry-js/blob/1758fa6e84333c9c43cc468c5e99dd3646f7e3c7/packages/opentelemetry-instrumentation/src/platform/node/types.ts#L45

Ah I think probably we made it required so authors would have to manually put * if they really meant to support all versions (it is very hard impossible to write an instrumentation that really works across all versions of some package).

Could we not lookup the version if we see * in the supported versions then ?

That's what I was thinking. If the supportedVersions.contains('*') we shouldn't have any reason to even attempt to find the package.json

Is there consensus on the solution?
The most recent suggestion was to only read the package.json if supportedVersions does not contain *.  This will resolve the lambda issue because the lambda instrumentation does have *.

I took a stab at this back in May, and ended up stashing it as  it didn't match the exact solution proposed above. I was honestly just hoping someone more experienced would pick it up.
It was extremely challenging to do a simple supportedVersions.contains('*') as the code is forked for two separate flows- Modules, and files. Additionally, the module.moduleVersion is also patched prior to these supportedVersion calls. Lastly, the moduleVersion is propagated to the module.patch, and file.patch functions.
I do not have enough understanding on the importance of these versions throughout this package, modules, and exports to be comfortable enough to change the behaviour of these methods.
This is the closest I got without any major refactoring:
https://github.com/open-telemetry/opentelemetry-js/compare/main...adambartholomew:aws-lambda-crash?expand=1
I could convert this to a PR, and move it through if there is sufficient interest.
This has been tested exclusively with unit tests, and should help raise the overall coverage on these classes. I have not loaded this into any real-world aws-lambda instrumentation projects for testing.

@vmarchaud The PR was merged (https://github.com/open-telemetry/opentelemetry-js/pull/2450) - should we close the ticket?


Use same font in search bar as elsewhere

Multiple fonts give a confused look.
Production:

Refactored:

As I mentioned, there is an issue where the font is different on Mac. This was changed and deployed some time ago, below is what it looks like on my Windows machine. I will be investigating this week why the font works only on some operating systems.


KAFKA-4134: log ConnectException at WARN

Simply log the connection refused instance.  If we're worried about spamming users, I can add a flag to make sure we only log this exception once, but the initial change is to simply log what we're given.  @ijuma looks like you were last to touch this code, would you mind having a look?

@cotedm This is still potentially very spammy, right? Default reconnect backoff is 50ms which means you'll get 20 of these (with stacktrace) per second that you have a connectivity issue.
We'd probably benefit from some helper that can rate limit certain log calls without permanently turning them off after the first time one is logged. Otherwise you can be missing information at a much later time due to a very short transient network issue at some completely unrelated time.

@ewencp I should think ConnectException would only happen if the remote process stopped listening, but you'd still be spamming users in that case. Let me add a general wrapper with a cooldown for log messages and use it here. Then if we find other spammy things, we can reuse it hopefully.

@ewencp I've added a LogRateLimiter utility with the method I would need as a wrapper. I think it's probably useful to have it for other scenarios so I kept it in commons/util, but if that doesn't make sense please let me know. I also hardcoded 1000 messages as the number we'll skip since I don't see a reason to make it configurable, but it might make sense to alert the user that the log message has been suppressed, what do you think?


use recent nightly for macOS

let's see if clearing the cache fixes the problem reported in rust-lang/cargo#4699

@homunkulus r+

:pushpin: Commit 66cce2b has been approved by japaric

:hourglass: Testing commit 66cce2b89a1343ca21e633237d62a8282cca5683 with merge f5d02ee0f4a36275da8335364129b7fdbbe76e49...

:sunny: Test successful - status-appveyor, status-travis
Approved by: japaric
Pushing f5d02ee0f4a36275da8335364129b7fdbbe76e49 to master...


Error when selecting a new column and immediately deselecting an existing column that has sorting applied

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1879
Originally created by @DouweM on 2020-03-20 16:21:49

Steps to reproduce:

Open report builder (design)
Select a column
Sort by this column by clicking table heading
Select a different column, which will trigger a query autorun
Immediately deselect the originally selected column before the first query completes, which will trigger another query autorun

Expected behavior:

Query runs successfully

Actual behavior:

Query fails with column "[originally selected sorted column]" does not exist error

Reason:
The newly issued query payload orders by the column, but doesn't actually select it.
When the column was deselected, it was removed from the order state, but when the first query that had the order applied succeeds, it restores the order state based on the query payload, and the now deselected column returns.
Regression introduced by https://gitlab.com/meltano/meltano/-/merge_requests/1537.

View 2 previous comments from the original issue on GitLab


Selected option text not updating when options are updated in Select component

On changing the options of the Select component, the options in the dropdown menu update but not the selected option's text.
Video for reference: https://www.loom.com/share/95b13b23e5744087bb89607653933f21?sid=9b58f644-c423-4b50-aca7-7d13f339403c

The input browser cache needs to be cleared via the clear prop, then you set the selected option.


Fix flow-rate in exercise 3.1

result_array_flowrate has values of temperature column do to a typo in the map function on line 375.

thanks a lot! [x] merged


[serde(default = .. )] in deep path

Playground
I'm not sure if it's a bug or a design.
I expect it to print consistent results in both cases. (Config { point: Point { x: MyInt(0), y: MyInt(1) } })

You are doing two different things here, which is why you get the different results. In the first case the Point struct is provided, but all fields are missing, thus they get filled by the default values on the fields, i.e., MyInt::default and MyInt::one.
In the second case the Point struct is missing and gets filled by Point::default. The derived Default implementation uses MyInt::default in both cases.
If you want to change the Default implementation of Point you need to implement it manually instead of deriving it.


fix: detect StreamingLessonPlan for mobile modal

We now use StreamingLessonPlan instead of Loading after the first message. This prevented the mobile modal from showing automatically after the first message

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


Improve the monthly process of allocation payments for GitHub Sponsors

Allocating payments to Collectives hosted by Open Source Collective that collect funds on GitHub Sponsors is becoming time consuming enough to consider automation. There are around 100 such Collectives at the moment compared with around 600 in total using GitHub Sponsors. This situation is not going to improve without some intervention.
Current monthly process

Login to GitHub Sponsors accounts on GitHub as the account admin. Go to the OSC account, select Fiscal Host and choose the Payout Export option. The report is then to be emailed to<EMAIL_ADDRESS>

Open the report and filter on the recent transactions
Log in to Xero and got to OSC dashboard to reconcile open transactions
Go to OSC Host Dashboard - Hosted Collectives tab
Identify the payout details in the report by searching the amount in the report and pulling the collective details out of the report.
Look for the collective, and use the process of adding funds manually to allocate the payout amount. We adding 5% for host fees and 5% for platform fees. Description added is "GitHub Sponsors [month] payment" and as an organization ensure to select github-sponsors.
Once funds are allocated, mark the amount as allocated in the report and reconcile the funds in Xero. For this use GitHub Sponsors as the source and description is the same as applied on the platform.
Any remaining unreconciled amounts are to be followed us with GitHub Sponsors project team

### Proposal
Around 80% of the projects that are on GitHub Sponsors and Open Collective use the same handle/slug. A Script that parsed the report from GitHub, matched the slug and added the necessary funds through the GraphQL API would alleviate a lot of the work. the script could output a report with funds allocated and runs left to allocate. From there the team member can allocate manually as above.

It seems more complicated to automate than what I thought, all the reconciliation is difficult.
If you could end up with a spreadsheet/CSV with the list of all collectives (with their slug) and the amount of money that needs to be wired, we could create some batching to Add Funds automatically.

It seems more complicated to automate than what I thought, all the reconciliation is difficult.
If you could end up with a spreadsheet/CSV with the list of all collectives (with their slug) and the amount of money that needs to be wired, we could create some batching to Add Funds automatically.

If you could end up with a spreadsheet/CSV with the list of all collectives (with their slug) and the amount of money that needs to be wired, we could create some batching to Add Funds automatically

@znarf this is what we already export from Github

If you could end up with a spreadsheet/CSV with the list of all collectives (with their slug) and the amount of money that needs to be wired, we could create some batching to Add Funds automatically

@znarf this is what we already export from Github

@alanna Sounds great. I tried to get access to such report today without luck, see on Slack. Please forward me a sample so I can have a look.

@alanna Sounds great. I tried to get access to such report today without luck, see on Slack. Please forward me a sample so I can have a look.

Creating pending orders would be a great step. @znarf if you'd require any changes to the data export to enable this, let us know the specifics and we can request them to Github. No guarantees about what they can do but we can ask.

Creating pending orders would be a great step. @znarf if you'd require any changes to the data export to enable this, let us know the specifics and we can request them to Github. No guarantees about what they can do but we can ask.

@znarf - OSC should pay for any significant develop time that gets spent on this, so please check with me or @piamancini before spending too much time, because we have to balance OSC's budget priorities, and while this process is currently painful, it is a functioning MVP we can live with for a little while longer if we have to.

@znarf - OSC should pay for any significant develop time that gets spent on this, so please check with me or @piamancini before spending too much time, because we have to balance OSC's budget priorities, and while this process is currently painful, it is a functioning MVP we can live with for a little while longer if we have to.

Just found this issues and encouraged @alinamanko to move the docuemtnation to https://app.gitbook.com/o/-LWSZizNMEjL8_DrMNdF/s/-MkoLSqv45-IqGUC_Gy-/c/tOoepGYtd0YVp2doS83p/github-sponsors
I've updated the title and the desripction above to include some improvements following my experience last month.

Bumping this issue. We had an ops deep dive session today and @alinamanko is identifying that this is now scaling beyond what's feasible to handle manually.
To clarify the scope, this is what we would like:

We download the CSV from github (example)
We'll check that the total from the data matches the total received in the bank manually
We upload the CSV somewhere a script can ingest it
The script creates transactions on OC that credit each Collective the amount for them on the spreadsheet

There is no need to do a pending order that needs to be confirmed. It should just automatically credit the money with no further action required, as a contribution to the Collective from the Github Sponsors org profile.
The main problem I see is Github uses an organization name on the CSV that does not necessarily match the OC slug. But if we can find a way to handle this we should be good to go.
@znarf @BenJam does this seem achievable?

This is prioritized in 2022 Q1 Sprint 1 as a use case for the API Project. We will deliver a command line tool that parse the CSV and create the Added Funds contributions using the API.
This will be manually triggered on a monthly basis by someone with enough technical knowledge (at first the engineering team, later other OSC admins).

@znarf one comment from me is that the slugs we have are not always a direct match to the names showing on the GitHub export. I am attaching the latest one here for context
sponsors-Open-Source-Collective-payouts-2022-01-25 (1).csv
.

@alinamanko I'm aware of this and the tool will be designed around this.
The tool is almost ready, we should be able to process the next batch with it. Just let me know when you have the CSV available.


Bug: Heading typography improvements

Chatting with @isabensusan today, we'd like to see headings use a base style from .tracking-tight.

Relates to https://github.com/open-sauced/engineering/issues/178


Add a custom install button

Relevant guidelines: https://web.dev/customize-install/

Thanks! I was using Chrome and the "Install App" in the menu worked.

Thanks! I was using Chrome and the "Install App" in the menu worked.


TDD support

Been using TDD feature on Flask. Might be better if same thing will be added to this jewel.

@Code-ReaQtor What features in particular are you looking for?

@seemethere
More like Flask's, usable with python unittest module:
http://flask.pocoo.org/docs/0.11/testing/
https://github.com/mjhea0/flaskr-tdd

After wsgi compliant, it could be integrated with WebTest and exposing fixture for pytest and unittest

After wsgi compliant, it could be integrated with WebTest and exposing fixture for pytest and unittest

This may be relevant: https://github.com/channelcat/sanic/pull/431

Think I can close this with #431


Add blockquote core component

See details here: https://www.w3schools.com/tags/tag_blockquote.asp
Should be easy to implement by looking at existing, similar core components such as paragraph or span!

I am also happy to address this issue

I think you're good to go! ;)

Closed via #88 thanks to @cameronnorman


Review page for broken links

This page has broken links due to hamburger menu control removal.

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

ID: 5045a1c3-a3ee-6da4-8961-c75b4f04025c
Version Independent ID: 07704e69-706d-893c-9bfd-853f6d51d7ee
Content: HamburgerMenu XAML Control - Windows Community Toolkit
Content Source: docs/archive/HamburgerMenu.md
Product: community-toolkit
GitHub Login: @nmetulev
Microsoft Alias: nikolame

Fixed in https://github.com/MicrosoftDocs/WindowsCommunityToolkitDocs/commit/ce6bad7954cefd3de0cfe653e02db173a642aba6


Fix wrong version in gRPCConfigVersion.cmake and grpc++*.pc

They use PACKAGE_VERSION to generate version information but
PACKAGE_VERSION may be overridden by find_package(). For example,
-DgRPC_CARES_PROVIDER=package with c-ares 1.16.0 overrides
PACKAGE_VERSION to 1.16.0. Because c-ares-config-version.cmake has the
following line:
set(PACKAGE_VERSION "1.16.0")

Setting PACKAGE_VERSION in version.cmake is a common CMake convention:
https://cmake.org/cmake/help/latest/command/find_package.html#version-selection

PACKAGE_VERSION
full provided version string

So we should use gRPC_CPP_VERSION not PACKAGE_VERSION to generate
gRPCConfigVersion.cmake and grpc++*.pc.

@nicolasnoble

Could someone review this?

Could someone reopen this?

Can I create a new pull request with the same change instead of waiting reopen?

I've created: https://github.com/grpc/grpc/pull/22982


Add loading content and add getX for state management

Hi @lordvins226 thank you for your pull request on loading and getX. I added two comments on your pull request, check it out.


Add designerSoftware in schema

I would like to include designerSoftware in schema

Hi! Could you elaborate, what is "designerSoftware" and what options would you suggest it has?

Something similar to the „Generator“ tag in HTML, maybe.

That is simply the name of the software in which the template has been made. Like Wasp3d, Loopic, RCC, RCCWebAnimator, AdobeAnimate. My idea is every software has some unique charactestics, And client software developer will get some idea about special care he must take.

Hmmm... The generator software should build templates, that work as specified. Did you have problems with some generated templates, that you could solve by adjusting your clients code? I can not imagen, what that could be. - My software "BluePrint" writes the "Generator" HTML tag. But just for advertisement :)

I suppose we could add an optional generator property to the specification, and just define it as a string - to be used for "information about who generated the html template"


Error saving current context

What is the issue?
EDIT: can reproduce an error by saving after a message that begins with ".
>>> /save mymodel
Error: command must be one of "from", "license", "template", "system", "adapter", "parameter", or "message"

this is after a long chat session with a previously saved model.
this is likely from the /save command not converting the session to the correct format for a saved model file.
I found that enclosing each message with """ newline message newline """ is the easiest way to avoid characters in the message from exiting the string context during parsing.
I can't tell without being able to view the data generated from the save command
I was able to reproduce another error
>>> "open quote
>>> /save stc
Error: unexpected EOF

also happens after a response
>>> "open quote
It appears that you've started quoting from somewhere, but^C

>>> /save stc
Error: unexpected EOF

my guess again is that the user message is not quoted during a save which means if it contains only one " the parser thinks it's a string and can't process.
could be solved by escaping quotes in all messages before saving?
note: works when " is not the first character of a message.
>>> \"open quote
>>> /save stc
Created new model 'stc'
>>> x"open quote
>>> /save stc
Created new model 'stc'

OS
macOS
GPU
AMD
CPU
Intel
Ollama version
0.4.0

What is the issue?
EDIT: can reproduce an error by saving after a message that begins with ".
>>> /save mymodel
Error: command must be one of "from", "license", "template", "system", "adapter", "parameter", or "message"

this is after a long chat session with a previously saved model. this is likely from the /save command not converting the session to the correct format for a saved model file. I found that enclosing each message with """ newline message newline """ is the easiest way to avoid characters in the message from exiting the string context during parsing. I can't tell without being able to view the data generated from the save command I was able to reproduce another error
>>> "open quote
>>> /save stc
Error: unexpected EOF

also happens after a response
>>> "open quote
It appears that you've started quoting from somewhere, but^C

>>> /save stc
Error: unexpected EOF

my guess again is that the user message is not quoted during a save which means if it contains only one " the parser thinks it's a string and can't process.
could be solved by escaping quotes in all messages before saving?
note: works when " is not the first character of a message.
>>> \"open quote
>>> /save stc
Created new model 'stc'
>>> x"open quote
>>> /save stc
Created new model 'stc'

OS
macOS
GPU
AMD
CPU
Intel
Ollama version
0.4.0

I have gotten "unexpected EOF" and then abrupt exit of the ollama interactive process three times in the last two days when doing /save {name}. I don't often want to save the context so this is 50% failure rate.
Mac M1 & M2.  #NeuralDaredevil model. (3.0GB)
No errors in server.log. I didn't check it right after the last crash so I'll be sure to do so the next time. I don't think the request made it to the back end however.


Package request: Game Cheetah

Project description
Cross-compatible cheat tool similar to cheat-engine for Linux

homepage URL: https://github.com/mkrueger/game_cheetah/

why would someone package cheats..


multiple level relationships ?

Question
In HiveList.  i can get a.b get b list
but when i use a.b.b1 want get b1 list, i get []

@rizzi37 could you please paste your code here?

closed~ i found func clear is Future.

closed~ i found func clear is Future.

i like to know how you make this strategy on hive

here is example~

void main() async {
  Hive.registerAdapter(PersonAdapter());
  var persons = await Hive.openBox<Person>('personsWithLists');
  await persons.clear(); // here clear before data, if no await, your data is no useful until you refresh your app in flutter or lost

  var mario = Person('Mario');
  var luna = Person('Luna');
  var alex = Person('Alex');
  persons.addAll([mario, luna, alex]);

  mario.friends = HiveList(persons); // Create a HiveList
  mario.friends.addAll([luna, alex]); // Update Mario's friends

  /// create in hivelist
  alex.friends = HiveList(persons); // Create a HiveList
  alex.friends.addAll([luna]); // from mario get alex friend  luna
  print(mario.friends);

  luna.delete(); // Remove Luna from Hive
  print(mario.friends); // HiveList updates automatically
}

in my app only different is use multiple box relationship.. here is in one box.


Fix error, require doesn't allow this type of destructuring

Oh, thanks, but I'm afraid I've already fixed this :)


Fix bug where Twillio was disabled in remote envs

@jeffk-kiva you'll like this one :)
Essentially the way that we load env.json values into process.env values is in the ConfigModule which is executed almost immediately, but not before the all Modules have been loaded. Because this referenced process.env as part of the top level module loading it executed before the ConfigModule had a change to update the process.env value. Moving it to a factory makes it so that it executes the function after all the modules have been loaded and after the ConfigModule has done it's thing. Yay env variables!
https://kiva.atlassian.net/browse/PRO-2453
Signed-off-by: Jacob Saur<EMAIL_ADDRESS>

wow.  This might be worth documenting in protocol-common so that someone else using it is aware that depending on how you initialize, the env processor might not kick in until after other modules initialize.


Use words not symbols

"20" or "about 20" or "more than 20"
https://github.com/ndorfin/cv/blob/ea19d9444eb5d4ff4f271477b1b02ae569807f7a/CV-ShaunO'Connell.html#L338

Done, thanks!


Re-write Running Kubernetes on Giant Swarm for clarity

This document doesn't "provide the goods" when it comes to introducing our offering and the "shared responsibility" with our customers
Please remember to

[x] Give the PR a meaningful title -- it will be shown in the release notes
[ ] Add (or remove) user questions associated with any updated docs

@marians apart from the spacing, is the content ok. Can I revert to an active PR?


Cannot register slash command with an option with a large amount of choices

When registering a slash command, if there are many choices for an option, the API request fails because the request has a maximum size of 25 bytes.
Basic code to reproduce: https://gist.github.com/downbtn/8afe14057faf822b2316930b62aa427f
Looking at the Discord API documentation for this function, it looks like this issue might be solved in the v10 API, and this library currently calls the v9 API endpoint.

Oh, I didn't see that table, I just saw that the paragraph didn't mention any length limit so I assumed it didn't exist in v10 API.


SFW

Do you always make a point of using the full name Smallest Federated Wiki, perhaps to encourage development of something like brand awareness?
The reason I ask is that in private emails and other writing I am starting to use "SFW" as did the friend who originally pointed me to your work.
Maybe a trivial point, but seemed worth mentioning.  You might have another shorthand you prefer to SFW and if so maybe it can be added to the "literature".

I use the term Smallest Federated Wiki when referring to this project. I use the term Federated Wiki when referring to the communities that I believe will emerge based on work explored first here. SFW is a reasonable shorthand when referring to this project among those familiar with it. This project has, since day one, been done in public on GitHub. You might enjoy reading some of the first commits.

I've added the above explanation to the FAQ.


DNN-7458 Optimized Type scanning

This code was cherry-picked from the speed-base-dnn-7458 branch (which was based on an old 7.4.2 build)

Reviewed, looks good.


December 19th hackathon meta-issue

Goals and priorities for the December 19th hackathon.
What people are working on

@azonenberg: implement write queueing (https://github.com/azonenberg/scopehal/issues/179)

Key to-do's
Feel free to work on other issues too. These are ones that I've flagged as either relatively easy or important.

Documentation

Expand section 14 (filters) of manual. We have ~90 filters. Only 9 are fully documented. 6 more have partial documentation, and the rest are just headings or a sentence of text describing the high level function of the filter.
Ensure all third-party dependencies are listed, along with their respective licenses https://github.com/azonenberg/scopehal-docs/issues/22

Protocol Decodes

Verify checksums in CAN https://github.com/azonenberg/scopehal/issues/333
Verify ECC in MIPI DSI https://github.com/azonenberg/scopehal/issues/328
Verify FCS in Ethernet https://github.com/azonenberg/scopehal/issues/55
MII https://github.com/azonenberg/scopehal/issues/291
RMII https://github.com/azonenberg/scopehal/issues/290
Manchester code https://github.com/azonenberg/scopehal/issues/112

DSP

Implement Fibre Channel golden PLL https://github.com/azonenberg/scopehal/issues/163
Implement decision feedback equalizer https://github.com/azonenberg/scopehal/issues/210

Driver support

Thorough stress testing of Rigol MSO5000 and Tek MSO5/6 driver
Add support for more trigger types on MSO5000
MSO5000 timebase/scale are wrong https://github.com/azonenberg/scopehal/issues/381
MSO5000 multimeter support https://github.com/azonenberg/scopehal/issues/310
Fix bitrotted/incomplete R&S scope driver https://github.com/azonenberg/scopehal/issues/59
Add Red Pitaya driver https://github.com/azonenberg/scopehal/issues/382

Interchange file formats

Rigol MSO5000 binary waveform import #287
WAV import https://github.com/azonenberg/scopehal/issues/226
VCD import https://github.com/azonenberg/scopehal/issues/228

Fix bugs/crashes

Windows RGBA/BGRA swap #299
GLEW fails to init under Wayland #277
Fullscreen mode is broken on Windows #273

Build/packaging

Get Windows CI builds to run unit tests #250
Make CI builds log status to IRC #247
Make CI builds run static analysis #240
Fix any remaining static analysis config problems #180
Make "make install" work, on both Linux and Windows #142
Set up initial binary release packaging using CPack #141

GUI

Finish the filter graph editor. Main missing feature is the ability to create new filters and assign them to waveform areas #161
When creating a filter decode that expects a digital input, allow analog inputs to be specified in the dialog if there's not already a threshold on that signal, and automatically create a 50% threshold filter for it.  #2

Art

We need a logo/app icon. Maybe come up with a catchier name than "glscopeclient" too. #204

Is it possible to contribute without compatible hardware? For example by loading a waveform from a file? I couldn't get the demo (complained about the transport being null), or siggen (only loads a hardcoded path) drivers working.
Wouldn't be interested to look into https://github.com/azonenberg/scopehal/issues/333 to learn the codebase.

Yes, you can work with saved files.
Here's a test waveform of some CAN traffic with the decode already set up for you: https://www.antikernel.net/temp/glscopeclient-candemo.zip. You can open it with "glscopeclient can.scopesession" or from the File | Open menu once glscopeclient is running. There's no way to open a file from the startup dialog yet, although we plan to fix that at some point.
The demo should work also, try "glscopeclient scopename:demo:null:blah" on the command line. Due to quirks of argument parsing you need to specify an argument to the NULL transport, that was probably your problem. If you can't get the demo working, open a separate ticket or join the IRC and we'll troubleshoot there.

@pd0wm Additionally, both #226 (WAV import) and #228 (VCD import) can be done without any actual hardware. I can provide test VCD files, and I'm sure you have audio files sitting around you can convert to WAV.
The CSV import code is probably a good reference point for that.


Missused Content-Disposition header in DataController

Description of the bug
DataController is checking if the request header "Content-Disposition" is set. This header should not be part of the request but in the subparts of a multipart request instead.
The check in Altinn.Core.Api is done here: https://github.com/Altinn/app-lib-dotnet/blob/v6.0.0/src/Altinn.App.Api/Controllers/DataController.cs#L699
The HttpRequest is also sent down to DataClient that also seems to misuse the header.
The api should not force clients to send http requests not adhering to the http standard
Steps To Reproduce

Create an altinn3 application
Try to upload an attachment without specifying Content-Disposition in the requestheaders, this is a valid http request
Controller returns error

Additional Information
No response

cc: @FinnurO

Renaming this isse to "Support for multipart upload of binary data in DataController". As it seems Content-DIsposition is set when using StreamContent or ByteArrayContent.
Tested with a simple client that uploads xml through StreamContent
Client code:
public async Task<string> ProcessUploadXml(string instanceId, byte[] attachment, string filename, CancellationToken ct)
{
    var uri = $"{_baseUri}/{_appUri}/instances/501337/{instanceId}/data?dataType=attachment";
    using (var content = new StreamContent(new MemoryStream(attachment)))
    {
        content.Headers.ContentType = new MediaTypeHeaderValue("application/xml");
        content.Headers.ContentDisposition = ContentDispositionHeaderValue.Parse($"attachment; filename=\"{filename}\"");
        var httppRequest = new HttpRequestMessage(HttpMethod.Post, uri);
        httppRequest.Content = content;
        var res = await _client.SendAsync(httppRequest);
        if (!res.IsSuccessStatusCode)
        {
            _logger.LogError("Upload to {URI} failed with statuscode: {StatusCode} content: {Response}", uri,res.StatusCode, await res.Content.ReadAsStringAsync());
            throw new Exception("upload failed");
        }

        var responseConrtent = await res.Content.ReadAsStringAsync();
        return responseConrtent;
    }
}

Headers logged on the server side:
      Connection: close
      Host: local.altinn.cloud
      Authorization: Bearer ##omitted##
      Content-Type: application/xml
      Content-Length: 33
      X-Real-IP: <IP_ADDRESS>
      X-Forwarded-For: <IP_ADDRESS>
      Content-Disposition: attachment; filename="demo.xml"

Multipart not supported today and Content-Disposition usage is ok. Support for multipart not requested at this moment. Closing with won't fix.


add request and response logger

This feature is used to detect any request method and url from API call, ande print response from API

LGTM
@rahmadfirman59 Thank you for your pull request!


Fix auto-downloading of files in OneDrive when doing dir

PR Summary
Related to the PR to enable recursion into OneDrive what's happening is that OneDrive online files are reparse points.  The current filesystemprovider automatically assumes a reparsepoint is a symlink so it opens the file trying to find the target of the symlink.  However, OneDrive online files are not symlinks so this causes the file to be downloaded so that it can be opened.  The fix is to use the same helper API in the other PR to check if it's a named surrogate and only then is it a symlink.  Otherwise, don't treat it as a symlink and don't try to retrieve the target.
Tested manually with my OneDrive folder.
PR Context
Fix https://github.com/PowerShell/PowerShell/issues/7152
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

@SteveL-MSFT, your last commit had 3 failures in PowerShell-CI-macos
Test-Connection.Ping.Force IPv4 with implicit PingOptions
Expected exactly $null, but got <IP_ADDRESS>.
at <ScriptBlock>, /Users/vsts/agent/2.152.1/work/1/s/test/powershell/Modules/Microsoft.PowerShell.Management/Test-Connection.Tests.ps1: line 91
91:             $result.Replies[0].Address              | Should -BeExactly $realAddress

Test-Connection.Ping.Force IPv4 with explicit PingOptions
Expected exactly $null, but got <IP_ADDRESS>.
at <ScriptBlock>, /Users/vsts/agent/2.152.1/work/1/s/test/powershell/Modules/Microsoft.PowerShell.Management/Test-Connection.Tests.ps1: line 106
106:             $result1.Replies[0].Address              | Should -BeExactly $realAddress

Test-Connection.TraceRoute.TraceRoute works
Expected exactly $null, but got <IP_ADDRESS>.
at <ScriptBlock>, /Users/vsts/agent/2.152.1/work/1/s/test/powershell/Modules/Microsoft.PowerShell.Management/Test-Connection.Tests.ps1: line 238
238:             $result.DestinationAddress | Should -BeExactly $realAddress

@PoshChan please retry macos,windows

@SteveL-MSFT, successfully started retry of PowerShell-CI-macOS, PowerShell-CI-Windows

Failing due to https://developercommunity.visualstudio.com/content/problem/607034/artifact-downloads-are-failing-201906.html

Close and reopen the PR to force Windows CI build working properly.

@iSazonov since @PowerShell/powershell-committee is ok with the change as it current exists regarding mode, if there are no code concerns, we should merge this


Fix bad version of spelling for building docs

Should fix travis build

Closed in favor of #265

sorry, missed that you already fixed it.

no problem :)


The flip face of flip cards and the reverse side of DFCs do not work on the bot

See #4157 for the genesis of this ticket.

[Erayo's Essence], [Dokai, Weaver of Life] and [Insectile Aberration] get no results.
[Erayo] does not print the flipped version just the unflipped version.

And Lim-Dûl type accents.

+    def test_dfcs(self) -> None:
+        self.finds_at_least('Delver of Secrets', 'Delver of Secrets')
+        self.finds_at_least('Insectile Aberration', 'Delver of Secrets')
+
+    def test_meld(self) -> None:
+        self.finds_at_least('Gisella, Blade of BAKERT', 'Delver of Secrets')
+        self.finds_at_least('Gisella, Blade of BAKERT', 'Delver of Secrets')
+        self.finds_at_least('Gisella, Blade of BAKERT', 'Delver of Secrets')
+
+    def test_flip_cards(self):
+        self.finds_at_least('Budoka Gardener', 'Budoka Gardener')
+        self.finds_at_least('Dokai, Weaver of Life', 'Budoka Gardener')
+
+    def test_accents(self) -> None:
+        self.finds_at_least("Lim-Dul's Vault", "Lim-Dûl's Vault")
+        self.finds_at_least("Lim-Dûl's Vault", "Lim-Dûl's Vault")

5ebaee4.


The HTTP request to the remote WebDriver server

OpenQA.Selenium.WebDriverException: The HTTP request to the remote WebDriver server for URL http://localhost:49719/session/fd495cece53f3013b447f334d2658916/elements timed out after 60 seconds. ---> System.Threading.Tasks.TaskCanceledException: The operation was canceled. ---> System.IO.IOException: Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request.
Selenium 4.5.1 ( .net Core ) - Any resolution

Can you give a bit more context?

Test method  exception:
OpenQA.Selenium.WebDriverException: The HTTP request to the remote WebDriver server for URL http://localhost:49707/session/16df674e735c388d463d5ae9f4ba12cf/elements timed out after 60 seconds. ---> System.Threading.Tasks.TaskCanceledException: The operation was canceled. ---> System.IO.IOException: Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request.. ---> System.Net.Sockets.SocketException: The I/O operation has been aborted because of either a thread exit or an application request.

Can you give a bit more context?

We are running a selenium script and execution fails after 2-3min

Excuse me, but you didn't really give more context.

Is the timeout that you configured in the capabilities 60 seconds?
Have you tried executing the request manually?
What kind of element are you targeting there?
Which browser do you target?
Does it happen in all browsers?

driver.Manage().Timeouts().ImplicitWait = TimeSpan.FromSeconds(60);

So this should not be related to the problem, but I would in general advice against setting (high) implicit timeouts.
Instead, it would be best to explicitly wait for certain things if needed.

Have you tried executing the request manually? - Yes

So, same outcome?
Did you then attempt to inspect the affected element manually before and after the timeout triggers?

Element Targeted - XPATH element , Web Based Application

I figured.
What I meant was what kind of UI element that is, e.g. pop-up, but, etc.?

Other Browser - I need the test to be run in Chrome only.

I think it could be worth a shot, but let's try some other stuff first.
Can you share any other stuff that might be helpful for debugging? E.g. screenshots, page source dumps, logs, request logs?

Thanks for your help ChristoWolf.
I was able to get some stacktrace if that helps :
AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
AwaitableSocketAsyncEventArgs.GetResult(Int16 token)
HttpConnection.SendAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
HttpConnection.SendAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
HttpConnectionPool.SendWithNtConnectionAuthAsync(HttpConnection connection, HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)
HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)
RedirectHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
HttpClient.FinishSendAsyncBuffered(Task1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts) HttpCommandExecutor.MakeHttpRequest(HttpRequestInfo requestInfo) HttpCommandExecutor.Execute(Command commandToExecute) --- End of inner exception stack trace --- HttpCommandExecutor.Execute(Command commandToExecute) DriverServiceCommandExecutor.Execute(Command commandToExecute) WebDriver.Execute(String driverCommandToExecute, Dictionary2 parameters)
WebDriver.FindElements(String mechanism, String value)
<.ctor>b__11_1(ISearchContext context)
I can attach few similar error : https://stackoverflow.com/questions/22322596/selenium-error-the-http-request-to-the-remote-webdriver-timed-out-after-60-sec

Adding Fluent wait updated the issue.

You mean that it's fixed now?
What exactly was the cause?
My only suspicion from your extended exception would have been that there were so many matching elements being found by FindElements that it timed out.

I tried with explicit wait as you mentioned but Fluent wait was working better , We were trying to reach the element after the selenium timeout. I just increased the wait time in fluent wait and it kept polling till the element was found.

They are equivalent, but whatever works best for you.
Great that your issues are resolved!


fix: holder cred-get-list returns only holder creds

Signed-off-by: Daniel Bluhm<EMAIL_ADDRESS>

cc: @mepeltier
Turns out this was an issue in the plugin rather than in the toolbox


fix a bug occurred the compilation error

1.0.3/src/node.h:251:34: note: candidate function not viable: cannot convert argument of
      incomplete type 'const void *' to 'const char *'
NODE_EXTERN v8::Local<v8::Value> Encode(v8::Isolate* isolate,
                                 ^

https://github.com/rvagg/nan/issues/264

@bnoordhuis Why was this signature changed in io.js? It also says not to use UCS2. 0.8 only took char * as well, should NanEncode use const void * or const char *?

@kkoopa That's because of iojs/io.js@535fec8 and iojs/io.js@56fde66c.

@bnoordhuis So now and later API will stay in const char *?

@XadillaX That's correct.

Is the bug present in 3.14? Should the UCS2 fix be backported to earlier versions?

Is the bug present in 3.14?

In principle, yes, although V8's CopyChars() implementation is just different enough that it doesn't seem to trigger gcc's SSE heuristics.  If you want to back-port the change, you have my blessing.

AppVeyor build failed.

any suggestion?

Ignore it, io.js does not work on windows.

Not yet ;) 1.0.4 will address this error I think.

+1

+1 on getting this fixed, so that my addon becomes io.js ready :)

Will this PR be merged? I'm in a hurry.

More or less. I've been holding off because I want to find a way of accounting for the API change regarding UCS2 in io.js. Will however not be backporting changes to older versions, as that was too much work. Been busy with other responsibilities.
ETA: the coming week

I'm hoping this fixed. :)

Fixed through #273.


Spyder unable to start as unable to link python kernel

Description

What steps will reproduce the problem?

Running spyder from terminal.

What is the expected output? What do you see instead?
The spyder UI hangs and then root kernel dies.

Please provide any additional information below
I tried to startup spyder (installed from Anaconda in OpenSUSE13.2 64 bit) from  a terminal. Suddenly it started linking console and then reports kernel dies.

Version and main components

Spyder Version:  2.3.4
Python Version:  2.7.9
Qt Version    :  4.8.6, PyQt4 (API v2) 4.11.3 on Linux

Optional dependencies
pyflakes >=0.5.0:  0.8.1 (OK)
pep8 >=0.6      :  1.6.2 (OK)
IPython >=1.0   :  3.1.0 (OK)
zmq >=2.1.11    :  14.5.0 (OK)
pygments >=1.6  :  2.0.2 (OK)
pandas >=0.13.1 :  0.15.2 (OK)
sphinx >=0.6.6  :  1.2.3 (OK)
psutil >=0.3    :  2.2.1 (OK)
rope >=0.9.2    :  0.9.4 (OK)
jedi >=0.8.1    :  0.8.1 (OK)
matplotlib >=1.0:  1.4.3 (OK)
sympy >=0.7.3   :  0.7.6 (OK)
pylint >=0.25   :  None (NOK)

If you installed Anaconda 2.2, please run this command
conda update pyqt

and try again. That should fix your problem.

Closing because of lack of respone


readme -- install VC for python 2.7

doing fresh install on another machine (win7) I ran into an issue on installing gevent via pip.
error  Unable to find vcvarsall.bat this is because python cant compile... upon some research I found there is a VC for python 2.7, and after installing it gevent installed just fine.

note that users should install VC for python 2.7 before trying to do pip install (no reboot needed).

just tell people to install subliminal and drop the list of the dependent install commands (could just list them under subliminal as a note.. but as its currently listed.. people may install the dependents manually before even getting to subliminal)

guessit is part of subliminal, so no need to install that manually..

VC for Python 2.7 -- http://www.microsoft.com/en-us/download/details.aspx?id=44266

Updated readme


Scrollbar should not expand to the navbar

Would be nice to find a way to stop it below the navbar.

It's possible to style it that way but the problem is that you have to set the overflow: auto property to a div and hide it on the body which will not trigger the loadMoreTweets action. Not sure if we can force this, just wanted to share in case other people have some ideas.

This has a PR here: https://github.com/sindresorhus/anatine/pull/65
@SamVerschueren the issue we're seeing is that you can't only style it in a way to limit the height. Is your screenshot on OSX? Ideally we'd have the default scroll bar and all its behaviors and just make sure it doesn't scroll above the bottom of the nav.

I know it has a PR, but this doesn't apply any style to the scrollbar itself. I just tweaked and moved some overflow properties of some DOM nodes. I just wanted to share, might be useful, or not :).
Yes it's on OSX but in the browser (refined-twitter). But the same thing applies here.

Maybe you can submit a PR of this so we can check it out? The current PR is not ideal for the reasons I mentioned above.

I've wanted to do this in the app to better solve a number of different problems (and ease adoption of something like react native web), but we've always held off due to the assumption (haven't retested recently) that div-scroll perf in iOS Safari isn't good enough.

@necolas and because it prevents iOS Safari from hiding it's URL bar and bottom bar.

Prevents Chrome hiding it too. They seem interested in fixing this though. Does the safari bottom bar overlay the content? If not, that might actually be an improvement over the default magic appearance. The sad state of Safari / web on iOS :(


Update database to match screenshot and notification domain classes

DATABASECHANGELOG still needs work

Not a big deal since this change isn't user-facing and thus shouldn't show up in the changelog anyway, but in the future, use the chore(xyz): Did some stuff with the things format for the commit messages


Sarkar/qwen ft

What does this PR do?
Add bucketing to Qwen training

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

closing this, opening new one: https://github.com/huggingface/optimum-habana/pull/1130