The ros package moveit_jog_arm
is now named moveit_servo
. If you were previously using moveit_jog_arm
you will need to do a find/replace for these phrases in your code base:
- jog_arm -> servo
- JogArm -> Servo
- jog_server -> servo_server
root@0a5d7aa235e9:~/ros_ws# rostest moveit_ros_planning_interface move_group_pick_place_test.test --text | |
... logging to /root/.ros/log/rostest-0a5d7aa235e9-10761.log | |
xacro: Traditional processing is deprecated. Switch to --inorder processing! | |
To check for compatibility of your document, use option --check-order. | |
For more infos, see http://wiki.ros.org/xacro#Processing_Order | |
xacro: Traditional processing is deprecated. Switch to --inorder processing! | |
To check for compatibility of your document, use option --check-order. | |
For more infos, see http://wiki.ros.org/xacro#Processing_Order | |
xacro: Traditional processing is deprecated. Switch to --inorder processing! | |
To check for compatibility of your document, use option --check-order. |
I hereby claim:
To claim this, I am signing this object:
- Sandbox build for wasm | |
- Debian downloads dependencies and then builds without network | |
- Cargo vender exists for this reason | |
- Build scripts exist for many reasons | |
- Build scripts that link to something need read-only file system access and to write to a target | |
- We need a capabilities for a build (network access, filesystem access) | |
- Figure out common patterns in build.rs and build libraries for build.rs that expresses capabilities | |
- Want developer experience with capabilities | |
- Person building the code is different from the author that knows what the crate needs | |
- cargo-vet was designed for for capabilities |