Closed bit-pirate closed 10 years ago
The ~/get_nodelet_manager_name service already returns the absolute name. Internally however, only the nodelet manager name itself is stored and used. This approach fails, when nodelets are loaded from within a namespace.
~/get_nodelet_manager_name
Suggestion:
Move the logic for retrieving the absolute name out of the service callback (https://github.com/osrf/capabilities/blob/master/src/capabilities/server.py#L915-L917) and into the LaunchManager class, which stores the name (https://github.com/osrf/capabilities/blob/master/src/capabilities/launch_manager.py#L100).
LaunchManager
Preparing a fix now.
@wjwwood PR #67 is my suggestion for fixing this. Let me know, if there is a more elegant/better way to implement this.
The
~/get_nodelet_manager_name
service already returns the absolute name. Internally however, only the nodelet manager name itself is stored and used. This approach fails, when nodelets are loaded from within a namespace.Suggestion:
Move the logic for retrieving the absolute name out of the service callback (https://github.com/osrf/capabilities/blob/master/src/capabilities/server.py#L915-L917) and into the
LaunchManager
class, which stores the name (https://github.com/osrf/capabilities/blob/master/src/capabilities/launch_manager.py#L100).