The user reporting the bug essentially describes he gets a warning, but does not mention any loss of functionality, nor any components which fail to function properly.
He's not using the components which depend on the bit of script which is not working (ie: the environment hook): the navigation stack would depend on the TURTLEBOT_MAP_FILE env var being set, but he doesn't use it.
LOSS-OF-CONTROL is even harder to justify: if this were a completely automated system, the map not being configured for the navigation stack could certainly lead to the robot not being able to navigate, but it would not even start up (ie: it would never have control, so it can't lose it).
turtlebot/3ea2c30
is labelledSOFTWARE:LIVENESS
. This seems hard to justify given the description:https://github.com/robust-rosin/robust/blob/93afbcb2ed1e74a9fbfa8eef7c2293ec8526f8d6/turtlebot/3ea2c30/3ea2c30.bug#L4-L14
The user reporting the bug essentially describes he gets a warning, but does not mention any loss of functionality, nor any components which fail to function properly.
He's not using the components which depend on the bit of script which is not working (ie: the environment hook): the navigation stack would depend on the
TURTLEBOT_MAP_FILE
env var being set, but he doesn't use it.LOSS-OF-CONTROL
is even harder to justify: if this were a completely automated system, the map not being configured for the navigation stack could certainly lead to the robot not being able to navigate, but it would not even start up (ie: it would never have control, so it can't lose it).