Stephen Brawner

It's unclear from just looking at the image. What version of SW are you using. Are you able to link the model that gives you these issues?

What version of SolidWorks are you using?

This has been a known issue with SolidWorks in the past and is not related to a bug with the exporter. Generally, SolidWorks versions from 2018 are most affected.

Other than finding difficulty when attempting to export your model, are there any issues you are finding with the tool itself?

It doesn't look like SolidWorks supports .OBJ exports by default, but it could be done with an add-in? Probably won't happen until I build out v2 of this tool. http://help.solidworks.com/2021/english/SolidWorks/scanto3d/t_exporing_files.htm

Step is recognized by Solidworks, but is not generally recognized by any tool that consumes URDFs.

I think resolving this issue could also resolve some rclpy related failures: https://github.com/ros2/rclpy/issues/267 https://github.com/ros2/rclpy/issues/513 Or at least they are related, the rclpy issues happen across multiple rmw implementations.

It certainly makes sense for restrictions to exist on this functionality. Maybe a request_shutdown would only come from a node that's been given elevated privileges, and only on the local...

I noticed a similar failure with `test_multithreaded__rmw_cyclonedds_cpp` on a 32-core machine. That test always runs `2 * max_concurrency threads`. https://github.com/ros2/system_tests/blob/02a3972276535714b03ea24d2ffaf2f5be13033f/test_rclcpp/test/test_multithreaded.cpp#L154-L255 Perhaps there could be a way to pass the requested...

During the above linked failures, the expected number of nodes doesn't match what it actually finds. When I was digging into this, the launch_ros node is running, but it's not...