Actions
Issue #9287
closedCopy API does depsolving twice
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
When we took out the code that tries to 'fix' depsolving problems, we left in the loop that assumes it's happening. This means that calling /copy/ with depsolving=True does the depsolving twice, every time, before continuing.
Given the performance- and memory-characteristics of the current depsolving processing, this is...Bad.
Related issues
Actions
On copy, depsolving was running twice. Taught it to Not Do That.
fixes #9287. [nocoverage]