search

roshub / vapor_master

high availability ros master
Apache License 2.0
17 stars 8 forks source link

[Bug] Loading params from yaml via roslaunch and <rosparam> not consistent with roscore #25

Closed HWiese1980 closed 5 years ago

HWiese1980 commented 5 years ago

Hi folks,

looks like I have found another bug. I have a YAML file that looks like this:

joints: 
  - (JointA, 0)
  - (JointB, 1)
  - (JointC, 16)

...basically.

When I load this YAML file in a launch file by means of <rosparam command="load" file="... and fetch the parameters afterwards with rosparam get joints I get the following returned from roscore: 

['(JointA, 0)', '(JointB, 1)', '(JointC, 16)']

... which obviously is a list.

But when I try to do that with vapor_master I get the following:

{'0': '(JointA, 0)', '1': '(JointB, 1)', '2': '(JointC, 16)'}

... which undoubtedly is a dictionary.

In order to use vapor_master as a true drop-in replacement, these things must be consistent.

sevenbitbyte commented 5 years ago

Thanks for the bug report @HWiese1980

We are currently reviewing PR #26 to address this issue.

sevenbitbyte commented 5 years ago

Fix has been merged and is now available in the snap store as version 0.3