-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add argument to run for submitting targets without IO checks #417
Comments
I think that we could do something like this:
So running |
That sounds great! I guess |
It's possible, but sounds like a very niche feature :) You could sounds the (almost) same problem by giving the dependencies to |
True! |
Great! I have commented on #416 separately. |
For larger workflows, the file IO checks can take a long time. In many cases this is appropriate, but often I'll know that no files have changed since my last
run
, in which case it is unnecessary to perform these checks in order to run targets that match the name regex. If the dependencies don't actually exist, I assume the jobs will just fail.E.g., say I am debugging a script and end up running the same target 5 times in a row. It would save a lot of time if I could tell it to just submit the job without checking dependencies. (This relates to why I like the context logging in #416 as I can copy the call and rerun interactively. But doing that for 100s of targets would be annoying :-) )
Perhaps a flag in
gwf run
could disable IO checks and just submit the jobs?Something like:
gwf run --no_io *my_target*
would then submit all targets that match *my_target* without checking IO and (and therefore without running missing dependencies).
The text was updated successfully, but these errors were encountered: