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

Set genealogy parent correctly to avoid multiple parents for graph refresh #14491

Conversation

Ladas
Copy link
Contributor

@Ladas Ladas commented Mar 24, 2017

Set genealogy parent correctly to avoid multiple parents for graph refresh

Only by doing child.parent = parent, we enforce that there can be on 1 parent at the time.

The hook variant is a slow n+1 for actual refresh, but it's used in some complex specs for graph refresh resolving cycles. The other is a custom saving code that does genealogy_parent assignment effectively and is currently used in AWS graph refresh.

Ladas added 2 commits March 24, 2017 15:27
Only by doing child.parent = parent, we enforce that there can be
on 1 parent at the time.
Only by doing child.parent = parent, we enforce that there can be
on 1 parent at the time.
@Ladas
Copy link
Contributor Author

Ladas commented Mar 24, 2017

@miq-bot assign @Fryguy

@Fryguy
Copy link
Member

Fryguy commented Mar 24, 2017

@Ladas Is this for backport? or is this master only?

@Ladas
Copy link
Contributor Author

Ladas commented Mar 24, 2017

@Fryguy should be only in Fine

@miq-bot
Copy link
Member

miq-bot commented Mar 24, 2017

Checked commits Ladas/manageiq@3a6786a~...fedeaa5 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
2 files checked, 0 offenses detected
Everything looks good. 🍪

@Ladas Ladas closed this Mar 27, 2017
@Ladas Ladas reopened this Mar 27, 2017
@Fryguy Fryguy merged commit 17528bb into ManageIQ:master Mar 27, 2017
@Fryguy Fryguy added this to the Sprint 57 Ending Mar 27, 2017 milestone Mar 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants