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
I don't have details yet on exactly when this happens, but the simple statement is: we have messages coming from Stack now that say "implicit adding package ...." based on command line flags and the like. The heuristics to generate these messages are completely wrong. We can either fix them, or decide that there's no reason to have these messages and delete them. I'm open to input.
The text was updated successfully, but these errors were encountered:
I believe that happens when you pass --flag pkg:flagname and pkg is a snapshot package. I think the reason for the message is related to the old behavior described in #3374 , which is that a package needs to be listed in extra-deps in order to have a flag applied to it.
Now that the restriction removed, this message indeed doesn't make any sense. I can't think of any decisions the user would make based on it, so my vote is to remove.
I don't have details yet on exactly when this happens, but the simple statement is: we have messages coming from Stack now that say "implicit adding package ...." based on command line flags and the like. The heuristics to generate these messages are completely wrong. We can either fix them, or decide that there's no reason to have these messages and delete them. I'm open to input.
The text was updated successfully, but these errors were encountered: