[wip] add example for submit and wait #205
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We should discuss the use cases for this particular example to distinguish when the user should use the FluxExecutor as opposed to a handle + jobspec + flux.job.submit Signed-off-by: vsoch <vsoch@users.noreply.github.com>
|
Update: I think we should clean up the use of jobspec first (e.g., being able to submit with one) and then figure out the context here and finish these up. I am also re-designing the flux-cloud submit given the new Flux Operator Python SDK and trying to figure out if I can minimize the number of specs of things (e.g., use a jobspec or a piece of one over there). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I started discussing this example with @grondo in slack - and we should discuss the use cases for this particular example to distinguish when the user should use the FluxExecutor as opposed to a handle + jobspec + flux.job.submit. A more advanced user is going to want to know why they should know about two ways to do the same thing, and if it's not the same thing, the pros and cons of the two approaches.
This is a WIP as it warrants further discussion!