…per as well

deleting robot package

* Add parameter to disable map server

* Move parameter check to getParameters

* Uncrustify

* Don't mark static layer as current until we have a map

* Make sure static layer gets initialized

Make sure static layer gets initialized, even with an empty layer, so it doesn't crash if you disable the map service and enable the obstacle layer

* remove map service from static layer

Only use map topic instead
Subscribe to map topic with default transient local volatility
Add parameter "map_subscribe_transient_local" (default=true) for backwards compatibility with volatile publishers

* Change AMCL to use only the map topic, not map service

* remove now-unused MapServiceClient

* uncrustify

* only set current_=true when first map received

* Fix nav2_costmap inflation tests.

* Fixing collision tester test.

* Revert "uncrustify"

This reverts commit 82f88a7.
This uncrustify failure is enforced differently depending on whether
we are on the dashing branch or on the master branch. This particular
commit is only appropriate on the dashing branch, but is already present
there.

removing old maintainers from navigation1

* change primitives to recoveries

* changing all over new bringups with nav2_recoveries

* renaming primitive_name -> recovery_name

Robot class to util

…or nav doesnt work

* I added a timeout to spin_until_future_complete, so rviz doesn't get frozen if something goes wrong in the navigation stack. I did some changes in the start navigation; - changed the funtion type to boolean - added returns to the funtion, so it will return false if something goes wrong. I changed goal_tool added a if statement to check if start_navigation doesn't return false before calling any other functions in goal_tool

* made the code cleaner and changed the error messages. Reduced the timeout value to 3 seconds. The timeouts will be parametrized in the future.

* added timeout parameter

Build tools - Run build_all.sh from any nested repo workspace & rename dependencies workspace for "nav" autocomplete

* I added a timeout to spin_until_future_complete, so rviz doesn't get frozen if something goes wrong in the navigation stack. I did some changes in the start navigation; - changed the funtion type to boolean - added returns to the funtion, so it will return false if something goes wrong. I changed goal_tool added a if statement to check if start_navigation doesn't return false before calling any other functions in goal_tool

* made the code cleaner and changed the error messages. Reduced the timeout value to 3 seconds. The timeouts will be parametrized in the future.

* added timeout parameter

* Update navigation_dialog.cpp

* Update navigation_dialog.hpp

* Update navigation_dialog.cpp

* Update navigation_dialog.hpp

* Fixing typo in dependencies

* Also remove some duplicate dependencies

* Fixing robot_state_publisher dependency

* Add back parameter to configure DWA rate

* Report out if we missed our control loop time.

All our builds have boost installed due to other dependencies, so
we've never run into this. The build farm must build with all other
dependencies removed somehow.

Signed-off-by: vinnamkim <vinnam.kim@gmail.com>