-
Notifications
You must be signed in to change notification settings - Fork 386
Spwaner: Load controller with remote only .yaml #2853
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Spwaner: Load controller with remote only .yaml #2853
Conversation
saikishor
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If i understood correctly it expects that the file exist on the same PC as the controller manager. I thought this PR is for cases when you want to load files of PC launching the command, but not on the PC the controller_manager is running
No its inverted its for cases where you don't have the I wanted to add the inverse as well if we want this. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #2853 +/- ##
==========================================
- Coverage 89.57% 89.47% -0.10%
==========================================
Files 152 152
Lines 18087 17732 -355
Branches 1470 1442 -28
==========================================
- Hits 16201 15866 -335
+ Misses 1297 1287 -10
+ Partials 589 579 -10
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Replaces: #2349
There are cases in which you want to spawn controllers running on a remote machine (robot) without the
controllers.yamlbeeing available on the local machine. This PR extends the spawner with the option to activate a controller on the remote machine without the need of havingcontrollers.yamlon your local machine.Example:
Open questions
How to pass controller type? In the spawner we need to know at least the
controller nameand thecontroller type. Usually we would parse the type from thecontroller.yamlbut since the file is not present on the local machine we need to pass the type. I choose to do:controller:typeas can be seen in the example. Is this good?How should we go about testing? In tests the file will always be present. I would just define the
.yamlin code, don't have the file present and test like this or are there any other suggestions?