Closed lambdaprime closed 7 months ago
Hi @marlow-fawn,
Thanks for trying jrosclient
We are looking into it and update you during the weekends
Hi @marlow-fawn,
Unfortunately we could not reproduce the problem.
Could you please enable debug mode and send the logs.
Thank you,
I'm seeing this same error when running my client in a Docker container on a Pi. This is not reproducing for me on any other platform though. Can help with troubleshooting if needed.
Hi @armadilloz
Thanks for trying jrosclient
Could you please enable debug mode and send the logs since we could not reproduce it.
Thank you,
Here are the logs: jros2java.zip
Hi @armadilloz,
We could reproduce the problem and are working on a fix. ETA is early next week.
Meanwhile you could try to workaround this problem by running ROS2 nodes with: export RMW_IMPLEMENTATION=rmw_cyclonedds_cpp
Regards,
Hi @marlow-fawn @armadilloz ,
The fix is ready and will be included in v6 we plan to release early March. Until then you can use prerelease version You will need to install it manually
Regards,
Hi @armadilloz @marlow-fawn @bibistellar,
We just published a new v6 release where this issue is fixed. In new release there are changes to messages metadata. If you have custom message classes defined then please regenerate them with msgmonster first. If you don't have custom messages then you can ignore it.
Regards,
This DOESN'T happen when creating a publisher node in the same process as the subscriber, so it doesn't seem to be an issue with the datatype any more. I can move this to another issue if you'd prefer.
Originally posted by @marlow-fawn in https://github.com/lambdaprime/jros2client/issues/9#issuecomment-1921945202