Search results

Missing xmlrpc carrier

Status: Open.

#2 In robotology-legacy/yarp-ros;

· randaz81 opened on Sep 5, 2023

Error generation from .msg files when using yarpidl_rosmsg

Status: Open.

#7 In robotology-legacy/yarp-ros;

· plinioMoreno opened on Jun 4, 2021

the Nodes system is not threadsafe by design

Status: Open.

#18 In robotology-legacy/yarp-ros;

· damn1 opened on Jul 11, 2018

Multiple publishers writing on the same topic cause segfault

Status: Open.

#8 In robotology-legacy/yarp-ros;

· randaz81 opened on Jun 27, 2018

No error when tcpros is not compiled, but yarp node is being used to publish to ROS topic

Status: Open.

#9 In robotology-legacy/yarp-ros;

· Tobias-Fischer opened on Apr 26, 2018

YARP-ROS: Do not know anything about type XXX

Status: Open.

#14 In robotology-legacy/yarp-ros;

· randaz81 opened on Nov 28, 2017

Document/clarify that multiple yarp::os::Node objects are allowed for process

Status: Open.

#17 In robotology-legacy/yarp-ros;

· traversaro opened on Sep 27, 2017

ROS Nodes registered in ROS Master using the <code>yarp::os::Node</code> are not unregistered when the object is deleted/on process exit

Status: Open.

#16 In robotology-legacy/yarp-ros;

· traversaro opened on Sep 26, 2017

/ros port removed by yarprun

Status: Open.

#15 In robotology-legacy/yarp-ros;

· randaz81 opened on Aug 11, 2017

yarp::os::Subscriber segfault when using callback

Status: Open.

#13 In robotology-legacy/yarp-ros;

· randaz81 opened on Mar 21, 2017

/ros port removed by yarp clean

Status: Open.

#10 In robotology-legacy/yarp-ros;

· randaz81 opened on Mar 21, 2017

wrong beaviour on opening bad named port with rosNode instantiated

Status: Open.

#12 In robotology-legacy/yarp-ros;

· aerydna opened on Dec 20, 2016