Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ros2 bag info and play are not able to open db3 bag files recorded on eloquent #1089

Closed
MichaelOrlov opened this issue Sep 14, 2022 · 0 comments · Fixed by #1090
Closed

ros2 bag info and play are not able to open db3 bag files recorded on eloquent #1089

MichaelOrlov opened this issue Sep 14, 2022 · 0 comments · Fixed by #1090
Assignees
Labels
bug Something isn't working

Comments

@MichaelOrlov
Copy link
Contributor

Description

Expected Behavior

ros2 bag info and ros2 bag play shall be able to correctly work with bags recorded on eloquent distro.

Actual Behavior

ros2 bag info eloquent-twist.db3
closing.
closing.
[INFO] [1663136366.540334404] [rosbag2_storage]: Opened database 'eloquent-twist.db3' for READ_ONLY.
Error when preparing SQL statement 'SELECT name, type, serialization_format, COUNT(messages.id), MIN(messages.timestamp), MAX(messages.timestamp), offered_qos_profiles FROM messages JOIN topics on topics.id = messages.topic_id GROUP BY topics.name;'. SQLite error: (1): SQL logic error

To Reproduce

  1. Download eloquent-twist.db3.zip
  2. Unzip eloquent-twist.db3.zip
  3. ros2 bag info eloquent-twist.db3
  4. ros2 bag play eloquent-twist.db3

System (please complete the following information)

  • OS: [Ubuntu Jammy]
  • ROS 2 Distro: [e.g. Rolling]
  • Version: [master]

Additional context

RCA:
The error happen when calling method SqliteStorage::get_metadata() because trying to select offered_qos_profiles field which is not present in topics table on ROS2 distros prior to the Foxy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant