Closed alaurenzi closed 2 years ago
Mitigated by a warning (instead of an error) in melodic-devel and noetic-devel.
I've just faced the same problem. Is there a new release coming with the fix?
@caioaamaral, of course, a new release is planned. But, I simply didn't have time yet to come back here. Please note, that I am the only active maintainer of this package and I am doing all this work voluntarily in my free time. I hope to find some time over the weekend to cut a new release, but I cannot promise. If you appreciate my work, please consider donating.
@caioaamaral, of course, a new release is planned.
Good to know, thanks for your effort in maintaining xacro
This issue has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/new-packages-for-noetic-2022-02-11/24292/3
This issue has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/preparing-for-noetic-sync-2022-02-14/24313/1
Comment evaluation is opt-in now: #310. New releases are triggered:
After a binary update, I am facing a bug where xacro will evaluate code sections that are commented out.
How to reproduce
Create a minimal xacro file with some commented out statement, save it as
text.xacro
Run
xacro test.xacro
Output:
Some info about my setup
Anything else I might help you with?