Savin
Savin
Also, regarding `@argo` - hopefully after PR #488 is merged in, we wouldn't need that decorator anymore.
The proposal looks good to me!
@romain-intel Not sure if I understood your comment properly, but my expectation is that the priority order will be the reverse of your comment - 1. `image` attr inside `@batch`...
@oavdeev But then would you expect folks to not be able to execute `python flow.py run --with batch:image=foo` where `flow.py` already has `@image` decorator as well. Today, you can execute...
Currently, we pick the larger of resources specified via `@batch` or `@resources`. It's a good point with `--with image:name=foo` - I think throwing an error when there are conflicts does...
@oavdeev The proposal LGTM!
How about we add both? It's usually a lot easier as a user for me to do `python flow.py list --my runs` or `python flow.py list --user=hamel runs`. We can...
Converted the PR to draft since it is not ready for review yet.
@tduffy000 We have an in-house implementation of `dataframe` which provides faster primitive operations with a lower memory footprint than Pandas. This is supported both on local instance and in the...
@thesillystudent Thanks for the PR. Conditional branching is kind of a mine-field in the sense that it makes reasoning about workflows (and state transitions) non-trivial for users. Do you have...