-
-
Notifications
You must be signed in to change notification settings - Fork 377
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
Flags created with --define appear to be incorrectly cached #3789
Comments
Mmm, this may not be related to |
With this I get:
|
@lihaoyi just fixed this issue in |
lefou
pushed a commit
to lefou/mill
that referenced
this issue
Oct 21, 2024
Fixes com-lihaoyi#3789. We just accidentally flipped the conditional and didn't have any tests that verify this behavior, so I added some example tests that also serve to explain the feature in the docs
lefou
added a commit
that referenced
this issue
Oct 22, 2024
Fixes #3789. We just accidentally flipped the conditional and didn't have any tests that verify this behavior, so I added some example tests that also serve to explain the feature in the docs. Backport of pull request: #3791 Pull request: #3795 --------- Co-authored-by: Li Haoyi <haoyi.sg@gmail.com>
Backported to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given this
build.sc
:I see the following:
Note that when not providing
--define=my-property=?
, it seems that the previous invocation ofmyProperty
is reused somehow, including theprintln
output.The text was updated successfully, but these errors were encountered: