Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixes #12166 - prevent over-counting in progress bar #154

Merged
merged 1 commit into from May 20, 2016

Conversation

domcleal
Copy link
Contributor

Defined types are evaluated twice, causing two RESOURCE lines to be
printed and double-counting. A set now tracks whether a resource has
already been evaluated and prevents progress being incremented again.

Resources such as concat 2.x and recursive file (dir) resources will
use eval_generate to add more resources into the catalog during
evaluation, which isn't in the initial count. These are now ignored by
tracking which resources were initially counted and only incrementing
the progress bar when those same resources are seen during the run.

Anchor and Kafo's own yaml_to_class resources are now also ignored to
improve the accuracy of the overall resource count.

Defined types are evaluated twice, causing two RESOURCE lines to be
printed and double-counting. A set now tracks whether a resource has
already been evaluated and prevents progress being incremented again.

Resources such as concat 2.x and recursive file (dir) resources will
use eval_generate to add more resources into the catalog during
evaluation, which isn't in the initial count. These are now ignored by
tracking which resources were initially counted and only incrementing
the progress bar when those same resources are seen during the run.

Anchor and Kafo's own yaml_to_class resources are now also ignored to
improve the accuracy of the overall resource count.
@ares
Copy link
Member

ares commented May 20, 2016

big 👏 it's much more accurate now, thanks @domcleal, merging

@ares ares merged commit 9377d25 into theforeman:master May 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants