Treat DragonStep
s as a Managed Steps
#6
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
DragonLauncher
now maps dragon run settings to aDragonStep
and regular run settings to aLoacalStep
to match behavior of existing launchers.The
DragonLauncher
treatsDragonStep
s as managed steps andLocalStep
s as unmanaged steps. TheDragonStep
s run commands are now tracked natively through the dragon run time and not proxyed through theproxyable_run_cmd
decorator.Remove unnecessary down casts to dragon specific entities. Unify
connect_to_dragon
code path for the main SmartSim process and the telemetry monitor.