You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ROS packages can make use of environment hooks -- shell scripts
that are executed, for instance, to set up environment variables.
In ROS Indigo, the core Turtlebot package introduced an
environment hook that depended on another package that was not
listed as a dependency in the package manifest. This caused error
messages to be printed to the terminal if the user did not have
the package installed.
The fix was to move the faulty parts of the environment hook to
the package they depended on.
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).
The text was updated successfully, but these errors were encountered:
turtlebot/3ea2c30
is labelledSOFTWARE:LIVENESS
. This seems hard to justify given the description:robust/turtlebot/3ea2c30/3ea2c30.bug
Lines 4 to 14 in 93afbcb
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).The text was updated successfully, but these errors were encountered: