Project

Profile

Help

Issue #9287

closed

Copy API does depsolving twice

Added by ggainey about 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
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

Copied to RPM Support - Backport #9298: Backport #9287 "Copy API does depsolving twice" to 3.14.zCLOSED - CURRENTRELEASE

Actions
Actions #1

Updated by pulpbot about 3 years ago

  • Status changed from ASSIGNED to POST

Added by ggainey about 3 years ago

Revision eb161f21 | View on GitHub

On copy, depsolving was running twice. Taught it to Not Do That.

fixes #9287. [nocoverage]

Actions #2

Updated by ggainey about 3 years ago

  • Status changed from POST to MODIFIED
Actions #3

Updated by dalley about 3 years ago

  • Sprint/Milestone set to 3.15.0
Actions #4

Updated by dalley about 3 years ago

  • Copied to Backport #9298: Backport #9287 "Copy API does depsolving twice" to 3.14.z added
Actions #5

Updated by pulpbot about 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF