-
Notifications
You must be signed in to change notification settings - Fork 251
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
Bag rewriter (C++) #920
Bag rewriter (C++) #920
Conversation
f7d2b83
to
5805c66
Compare
85aaa4e
to
b390a86
Compare
277d612
to
7e2f01b
Compare
Signed-off-by: Emerson Knapp <emerson.b.knapp@gmail.com>
Signed-off-by: Emerson Knapp <emerson.b.knapp@gmail.com>
4adb141
to
200ae66
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only seeing one really small comment issue (apart from the build issue). Not sure if it's something we need to bother with, but thought I'd bring it up anyways.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks reasonable to me. just one nit on documenting serialization format selection.
Gist: https://gist.githubusercontent.com/emersonknapp/118ff3d83fe59438cad609306b4c102d/raw/8368bbbc8a74f487474f3474161702962fbd4cb6/ros2.repos |
7ba2e3e
to
2ce7cc9
Compare
Signed-off-by: Emerson Knapp <emerson.b.knapp@gmail.com>
2ce7cc9
to
e9c33e7
Compare
Signed-off-by: Emerson Knapp <emerson.b.knapp@gmail.com>
Noting here explicitly. The OSX CI build queue is backed up by ~12 hours right now because there is only a single executor online and some very long builds are stacked up. Will merge now, and if something is warning on OSX then I am happy to fix it then. |
Whoops. We were doing some network maintenance and we forgot to reenable them when that was finished. All 4 are back online now, FYI. |
Looks like the one from this morning failed on some networking issue, and the one from 3 hours ago got remove from the queue somehow (Jenkins doesn't have actual entities for pending builds, which drives me bananas - if you delete your build from the queue then everybody else's badges from behind you in the queue are wrong because the ID gets reassigned to the next queue item ) Rebuilding for just in case, though #921 will catch any problems |
next_messages.resize(input_bags.size(), nullptr); | ||
|
||
std::shared_ptr<rosbag2_storage::SerializedBagMessage> next_msg; | ||
while (next_msg = get_next(input_bags, next_messages)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This introduced a warning message into the buildfarm. See nightly_osx_debug#2246.
It's probably unintended usage, would you take a look? @emersonknapp
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is intended usage - as noted above I wasn't 100% sure that OSX would be happy. Will add the parentheses suggested by Clang ASAP.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👨🌾 This test regression is probably related to this PR as well: https://ci.ros2.org/view/nightly/job/nightly_win_rel/2137/
|
@Blast545 no, that is an existing flaky test - there is no way for this PR to have affected recording functionality |
This reverts commit 2abc509. Signed-off-by: Jorge Perez <jjperez@ekumenlabs.com>
Implements main functionality of #831
Depends on #924
Depends on #923
Adds a
bag_rewrite
API that takes Reader(s) for existing bags and writes all their messages to Writer(s) with specifiedStorageOptions
andRecordOptions
.Does not expose the feature to Python/CLI - that is implemented in followup PR #921