-
-
Notifications
You must be signed in to change notification settings - Fork 343
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
Calling an exclusive command from a non-interactive command results in a NoSuchElementException
#3875
Comments
NoSuchElementException
NoSuchElementException
I guess this makes sense; the evaluator hardcodes the assumption that all exclusive commands run after the non-exclusive stuff, and so when the non-exclusive command tries to look up the exclusive upstream task in the list of non-exclusive upstream task it fails to find it. It feels like the correct thing to do here is to raise a proper error when a non-exclusive task depends on an exclusive task |
Another resolution could be to not necessarily run exclusive tasks at the end but only isolated (non-parallel to any other) but still before all its dependencies. |
As a side note, in If we could have isolated commands not only in the end but also anywhere in the middle of the execution plan we could also run clean builds in Mill with a single run. E.g. |
Yeah having some way to order commands would be nice, so |
When running the following command:
Mill errors out with the following error:
If the
cleanClient
commandinteractive = true
, the error goes away.The text was updated successfully, but these errors were encountered: