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

[Gaprindashvili] Fix saver strategies spec #17194

Closed

Conversation

Ladas
Copy link
Contributor

@Ladas Ladas commented Mar 23, 2018

Few tweaks that were refactored upstream, we need for passin g-release specs, after backporting https://github.com/ManageIQ/manageiq/pull/17020/files#diff-cd53f672c80e0bcb003c0fb0dd75bf05R223

Fixes the failed CI

Allow association to be nil and always stringify reference. Not
defined association should be nil not []. Reference for
db_strategy needs to be stringified for g.
In g release, lazy_find accepts only string
@miq-bot
Copy link
Member

miq-bot commented Mar 23, 2018

Checked commits Ladas/manageiq@f77019a~...86a18b4 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
2 files checked, 0 offenses detected
Everything looks fine. ⭐

@Ladas
Copy link
Contributor Author

Ladas commented Mar 23, 2018

@miq-bot assign @agrare

@miq-bot
Copy link
Member

miq-bot commented Mar 23, 2018

This pull request is not mergeable. Please rebase and repush.

@Ladas
Copy link
Contributor Author

Ladas commented Mar 23, 2018

@cben this is what I had to change to make the specs pass

All we really need to do is lazy_find(whatever.to_s) and to define :association. I'll send the fix for association being set to nil to upstream first.

@Ladas Ladas closed this Mar 23, 2018
@cben
Copy link
Contributor

cben commented Mar 25, 2018

Cool. Sounds like you got it covered? Let me know if I can help.

@Ladas
Copy link
Contributor Author

Ladas commented Mar 26, 2018

@cben you will need to send #17020 for G-release, they reverted it because of the failed CI. We can talk there, to make sure it passes the g-release CI.

@cben
Copy link
Contributor

cben commented Mar 26, 2018

hmm, if lazy_find accepts only strings, how will BigDecimals work?
but in real life I don't need lazy_find by any decimal column. let me figure out if I can rewrite the test...

UPDATE: #17214

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.

4 participants