Reuse xmlrpc connections everywhere#1471
Conversation
6bd5022 to
9cc8b31
Compare
|
Any comments on this? We use this feature (backported to our kinetic branch) on our robots for 4 weeks now without any problems. |
|
Shouldn't |
@mgrrx Do you mind responding to this question? |
|
added a surrounding lock. We are running with this patch since August 2018 and didn't have any issues so far. |
5918edd to
77bb247
Compare
|
rebased against current melodic-devel branch |
|
CI fails due to unrelated reasons as far as I can tell |
Unfortunately the Noetic jobs can't pass until all dependencies have been released. That shouldn't block this PR to be merged though. |
|
Please rebase the patch to resolve the conflicts. |
77bb247 to
a67d52e
Compare
|
done |
|
Thanks for the patch. |
|
This change caused a regression: #1913. |
I noticed that xmlrpc connections are still not always reused since, due to circular import dependencies, the proxy class in rospy.msproxy can't be imported into these modules:
Current behavior
The current behavior is that a bunch of connections to the master are created and closed when running e.g. rospy.init_node:
(sudo tshark -i lo -f "dst port 11311 or src port 11311")
This continues when one creates e.g. a Subscriber:
And a second one:
Patched version
With the proposed change this behavior changes to:
rospy.init_node
First Subscriber:
Second Subscriber:
Implementation: