-
Notifications
You must be signed in to change notification settings - Fork 121
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
self.node.get_clock().now().to_ros_msg().unwrap()
doesn't work anymore
#385
Comments
Ok, I have a workaround for now. So you can fill the timestamp of a ros2 header correctly:
As you can see right here, your
From my point of view, this issue should definitely remain open, as timestamps are an essential resource for nodes, especially when processing sensor data. I am currently having heated discussions with someone who is using an algorithm for determining angular ranges from |
@Guelakais do you happen to have the
Can you paste a link to the ticket where you asked for this feature? Would be a nice addtion, though perhaps using the |
#381 |
@esteve it occurs to me that the vendored message packages could create a lot of confusion when building the What would you think if we put some logic into the vendoring script to check whether the Rust bindings for the messages are available in the workspace before we vendor them? We would then install the vendored bindings in a way that they can be used as if they're the upstream bindings. |
building the corresponding Ros distribution in the same workspace as ros2 rust is, in my experience, quite extraordinary. Normally, the classic ros2 developer relies on the corresponding Something basic: If in doubt, you should include your dependencies in |
@mxgrey yeah, I agree, the vendored interfaces can complicate things (this ticket is an example of that). The core issue is that we wouldn't need to this if we could get the generator included in the buildfarm. Or at least, we could do things differently.
That's a good idea, it'd make things less confusing and we'd still be able to push rclrs to crates.io |
@Guelakais the infrastruture for generating code for messages is rather complex, hence why it's not as streamlined with However, you'd still need to declare dependencies in Cargo.toml so that both |
Ok, I've been dealing with this bug all evening. For some reason rclrs keeps replacing |
How do you imagine how the timestamp should be filled properly and why does this error first occur today? What have you done?
The text was updated successfully, but these errors were encountered: