Change the multilayered design to use Futures to handle nested content
With the addition of DeclarativeContent.future, we ought to be able to use that to handle any nested content without loops or the layered pipeline we currently use. With that refactor in place, the pipeline will be flat and each stage will only need to be used once, which will eliminate the need for reentrant ProgressBars described previously.
A previous commit for pulp_deb used this design pattern, and will be helpful for the implementation here:
It should be noted that pulp_deb no longer uses that pattern to get around the min_size deadlocking problem, so I'm going to set 4296 as as blocker. https://pulp.plan.io/issues/4296
Current implementation does not use the ProgessBar. This is because the ProgressBar returns unexpected results when the same Stage is used multiple times as we do in Docker sync.
#7 Updated by firstname.lastname@example.org 11 months ago
The problem in the original description is due to a limitation of the Stages API. If the stages API allowed stages that come after the Artifact download stage to send items into the queue for the Artifact download stage, the Progress Bar inside the Artifact download stage would report accurate results. @bmbouter is going to add another story to add support for such a use case. Once that is implemented this story should be updated to state that pulp_docker needs to be refactored to use that feature.
Please register to edit this issue