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
Presently the ports for Fleet Adapter API servers are hardcoded in the fleet_manager files. This could lead to conflicts in systems. We could rely on something like portpicker to return an available port to use.
We should try to get a rosdep key for the dependency as well so that rmf_demos can be distributed via the buildfarm.
Implementation Considerations
No response
Alternatives
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Before proceeding, is there an existing issue or discussion for this?
Description
Presently the ports for Fleet Adapter API servers are hardcoded in the fleet_manager files. This could lead to conflicts in systems. We could rely on something like portpicker to return an available port to use.
We should try to get a rosdep key for the dependency as well so that rmf_demos can be distributed via the buildfarm.
Implementation Considerations
No response
Alternatives
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: