feat: Return launch and connection info from standalone launcher dry-run #3576
+88
−25
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.
Use case of the
dry_run
argument of thelaunch_fluent()
to use with external launcher for launching Fluent in a different machine./mnt/shared
in the server machine and\\server\shared
in the client machine.SERVER_INFO_DIR
to/mnt/shared
in the server machine and\\server\shared
in the client machine.launch_fluent(fluent_path=<path to fluent exe as in the server machine>, dry_run=True)
will return a tuple containing Fluent launch string and the absolute path of the server info file in client.connect_to_fluent()
with the server info file path returned above.