You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New features take time and effort to create, and they take even more effort to maintain. So if the purpose of the feature is to resolve a struggle you are encountering personally, please consider first posting a "trouble" or "other" issue so we can discuss your use case and search for existing solutions first.
For (2), there is the question of what we mean by "cancel". When one branch throws an error, some of its siblings may not have started yet, whereas others may already be running. I would prefer to cancel the former and let the latter keep running. Reasons:
It seems friendlier for users and easier for them to understand.
Prework
Proposal
Suggested by @hadley in #1310 (comment): if a target fails, then
For (2), there is the question of what we mean by "cancel". When one branch throws an error, some of its siblings may not have started yet, whereas others may already be running. I would prefer to cancel the former and let the latter keep running. Reasons:
clustermq
doesn't support cancellation either AFAIK.)targets
:error = "trim"
will treat currently running targets the exact same way aserror = "abridge"
Overall, I think
error = "trim"
will be a nice addition totargets
.The text was updated successfully, but these errors were encountered: