Actions
Issue #7741
closed
Code doesn't handle requirements.yml sources with different api versions
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
From what I gather from the code, it doesn't seem to handle that sources in requirements.yml may have different api versions. It just uses the api version from the remote.url:
Related issues
Updated by fao89 about 4 years ago
- Related to Refactor #7777: As a developer I want collections sync machinery easier to maintain added
Updated by bmbouter almost 4 years ago
- Status changed from NEW to POST
- Assignee set to bmbouter
Added by bmbouter almost 4 years ago
Updated by bmbouter almost 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp_ansible|2ab95bd8a607262c6ec220fd0ab43d6351b10ea9.
Updated by fao89 almost 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Refactors sync to use asyncio more and many tests
The previous sync machinery design was very complicated due to treating the asynchronous coroutines as synchronous code. This rewrites the sync code to have the coroutines track the work instead.
In doing the rewrite several bugs were fixed also:
It also makes many test improvements:
closes #7739 closes #7741 closes #7777