Skip to content

receiving different imu data after migrating to ros2-4.1.0 from ros2-4.0.0 #119

receiving different imu data after migrating to ros2-4.1.0 from ros2-4.0.0

receiving different imu data after migrating to ros2-4.1.0 from ros2-4.0.0 #119

Triggered via issue July 6, 2024 00:36
Status Success
Total duration 15s
Artifacts

new-issues.yml

on: issues
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
triage
The following actions uses node12 which is deprecated and will be forced to run on node16: github/issue-labeler@v2.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
triage
The following actions uses Node.js version which is deprecated and will be forced to run on node20: github/issue-labeler@v2.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
triage
Unexpected input(s) 'enable-versioned-regex', valid inputs are ['repo-token', 'configuration-path']