Philipp Oppermann
Philipp Oppermann
Closing on favor of https://github.com/dora-rs/dora/pull/495
Providing the ticks directly by dora has some advantages: - no need to compile and distribute an extra node -> the timer is always available - we can generate the...
How about we create a branch called `next` where we point all breaking changes? This way, we could implement this step-by-step across multiple PRs and do the breaking release once...
Good point! Let's try to keep things backwards-compatible for now then.
I created a PR at https://github.com/dora-rs/dora/pull/478 to implement the new dataflow parsing logic without the extra nesting behind the `custom` field. I was able to implement this in a backwards...
Yes, we don't very the output, as it's not deterministic enough. We just check the exit code of the process, which should be `!= 0` when an error occurs. We...
Thanks for the suggestion! This seems like a good idea in general. Right now we have other things with higher priority, but I put it in our backlog. (If someone...
This seems related to https://github.com/jhelovuo/ros2-client/issues/25. Messages send at the beginning might be lost because it takes a bit until ROS2 creates the connection. You can avoid this by choosing reliable...
Thanks for the PR! This seems to fail our CI job unfortunately with the following error: > /usr/bin/ld: cannot find -lpcap: No such file or directory Given that the job...
You could try to test the two nodes separately against ROS2 nodes: 1. Verify that ROS2 messages sent by the Dora C++ node are seen by ROS2. 2. Verify that...