[Rock-dev] [rock] #360: port_driven stops working after reconfiguration

[rock]

#360: port_driven stops working after reconfiguration
-------------------------------------+------------------------------------
 Reporter:  christian.rauch          |       Owner:  rock-dev-mailing-list
     Type:  defect                   |      Status:  closed
 Priority:  major                    |   Milestone:
Component:  base                     |  Resolution:  worksforme
 Keywords:  port_driven, updateHook  |
-------------------------------------+------------------------------------

Comment (by christian.rauch):

 I forgot to mention, that I am using syskit (next) to write data to that
 task.
 As it turned out, this behaviour depends on who is starting the task after
 it has stopped. If the task is stopped and started by syskit (through the
 composition writing the data), the data arrives and the updateHook is
 triggered. If the task is started manually (e.g., by reconfiguration in
 the TaskInspector), syskit will not recognize that, when the composition
 is started and writing data again.

 E.g, when syskit is starting the task there will be:
 {{{
 [...] not reconfiguring [...]: the task is already configured as required
 [...] applied configuration [default] to [...]
 [...] was already configured
 [...] starting [...]
 }}}
 in the logs, which does not occur if the task was started not in the scope
 of syskit and the composition is executed.

-- 
Ticket URL: <https://rock.opendfki.de/ticket/360#comment:2>
rock <https://rock.opendfki.de>
rock: the robot construction kit