~wooksong/nnstreamer-ros/+git/tizenport-ros-comm:indigo-devel

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

c646e0f... by Dirk Thomas on 2017-03-06

1.11.21

81b2577... by Dirk Thomas on 2017-03-06

update changelogs

6506111... by Dirk Thomas on 2017-03-06

Merge pull request #1008 from ros/backports_indigo

changes between 1.11.20 and 1.12.7 for backporting

a198566... by John Morrissey on 2016-12-16

terminate underlying 'rosbag {play,record}' on SIGTERM

83d3935... by Minsu Kim <email address hidden> on 2017-01-16

fixed UDP block number when EAGAIN or EWOULDBLOCK (#957)

* fixed UDP block number when EAGAIN or EWOULDBLOCK

48ef2a1... by Jannik Abbenseth <email address hidden> on 2017-01-10

[rospy] made get_published_topics threadsafe (#958)

* [rospy] made get_published_topics threadsafe

017aa89... by IsaacS on 2017-02-16

[roslaunch] Indicating <node> tag when it is actually a <test> tag is confusing.

For example, [this warning msg](https://travis-ci.org/wg-perception/people/jobs/202019288#L3737) (in this [PR](https://github.com/wg-perception/people/pull/49)):

 ```
 * WARN: unrecognized 'group' tag in <node> tag. Node xml is <test name="$(arg testnode_name)" pkg="rostest" test-name="hztest_test" type="hztest">
    <group unless="$(arg expected_success)">
      <node args="-r 0.5 $(find face_detector)/test/face_detector_noface_test_diamondback.bag" name="play" pkg="rosbag" type="play"/>
      <param name="hz" value="0.0"/>
    </group>
```

This is confusing because the tag in question is actually `<test>`, not `<node>`. Although the warning message refers to the exact <test> tag, I didn't try to read it because I was told the issue is with <node>, not <test>.

With this PR the message becomes a bit verbose but hope the readers get better idea.

579619b... by "Isaac I.Y. Saito" <email address hidden> on 2017-02-18

[rostest] Fix type in hztest assertion (#992)

d539346... by Dirk Thomas on 2017-02-01

throw exception instead of accessing invalid memory

9fa1d07... by Brett Ponsler on 2016-11-10

Fixing logic issue causing cache not to be saved properly.