[Rock-dev] [rock] #368: syskit: bad port name gets resolved when mapping from service to composition to specialization
rock
noreply at opendfki.de
Thu Nov 7 12:27:26 CET 2013
#368: syskit: bad port name gets resolved when mapping from service to
composition to specialization
-----------------------+-----------------------------------
Reporter: anonymous | Owner: rock-dev-mailing-list
Type: defect | Status: new
Priority: major | Milestone:
Component: base | Keywords:
-----------------------+-----------------------------------
I have a composition like this
{{{
class C < Syskit::Composition
add Base::PoseSrv, :as => 'pose'
script do
port_r = pose_child.pose_samples_port.reader
poll do
port_r.read_new
end
end
end
}}}
This fails at execution time when used with the
SLAM::Odometry.use(Odometry::Skid) network. Looking into it with pry leads
me to think that the port name (port_samples) does not get properly
resolved to the Odometry::Skid port name (from the specialization), but
only to the one from Base::OdometrySrv from the SLAM::Odometry original
definition
--
Ticket URL: <http://rock.opendfki.de/ticket/368>
rock <http://rock.opendfki.de>
rock: the robot construction kit
More information about the Rock-dev
mailing list