-
Notifications
You must be signed in to change notification settings - Fork 913
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rospy client does not cache parameters #1575
Comments
Checkout #1515 |
Interesting, seems like #1241 introduced this regression in melodic. I didn't notice this yet since at Magazino we are still on kinetic and this feature was not backported. |
I think the more appropriately alarming title for this issue is 'rospy hits rosmaster on every log invocation'. Thanks for the caching fix @mgrrx, we're going to run our robots on locusrobotics#10 for a while as validation. |
This was resolved by #1515. |
rospy client does not cache parameters despite having a parameter cache, and there is no option to enable it:
https://github.com/ros/ros_comm/blob/melodic-devel/clients/rospy/src/rospy/msproxy.py#L119
This is in contrast to roscpp which has the option to cache parameters, and it is on by default.
This is easily observed by running the "talker" tutorial for both roscpp and rospy and monitoring communications on port 11311 with wireshark. The rospy version will continuously send a
getParam
request for the parameter/rosout_disable_topics_generation
without subscribing, the roscpp will only send one and will subscribe to the parameter.Since roscpp does cache parameters, it makes sense to enable this for rospy as well, unless I am missing something.
The text was updated successfully, but these errors were encountered: