Fix solve dance caused by verification tasks #302
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I've seen an issue with the verification task in two instances after upgrading to 23.9.0:
base
environment, it insisted on downgrading Python 3.9.14 to 3.9.9. I requested 3.9.14 again, it installed. But runningconda install conda-libmamba-solver=23.9.0
(which should be a no-op, because it's already there), asked for the Python downgrade.grayskull
environment, I ranconda update --all
and it successfully updated everything. Running it again, asked for a slightly different solve. A third time, it undid the previous one. And so on: it keeps bouncing between two solutions.Since this is not ideal, I suggest we remove the verification task (which is only needed to "repair" a force removal) until we learn more about. It'd be a good moment to do proper consistency checks before handling the install request, as conda classic does.
Dance logs
Checklist - did you ...
news
directory (using the template) for the next release's release notes?