-
Notifications
You must be signed in to change notification settings - Fork 296
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
Refs #35713 - correctly call methods with kwargs #10845
Refs #35713 - correctly call methods with kwargs #10845
Conversation
@ofedoren I think this would also be relevant to our Ruby 3 work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, thanks for notifying.
LGTM, and I'd just merge it. There is no reason to hold it.
And now I'm really curious why it worked at the first place...
It was broken by #10744 because that PR both added the methods and called them incorrectly, and I didn't catch it before merging. |
@jeremylenz then shouldn't this be |
I usually don't use "Refs" because I don't trust our automations (mostly Jira/Bugzilla) not to duplicate or mess up tickets. I can change it if you feel strongly. |
Refs should be used if it's the same issue, within the same release. Otherwise you mess up automation, like cherry picks |
7ca7eec
to
0250c25
Compare
updated Redmine and commit messages. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK via #10846 (review)
(cherry picked from commit 3ac7cdd)
(cherry picked from commit 3ac7cdd)
What are the changes introduced in this pull request?
In #10744 package_names_for_job_template was extracted into two new methods,
yum_names_for_job_template
anddeb_names_for_job_template
.These new methods accept only keyword arguments, but are called only with regular non-kwargs.
This change fixes that and properly calls the methods with kwargs.
Considerations taken when implementing this change?
What are the testing steps for this pull request?
Install or remove a package via the new host details UI and make sure that the job template renders without errors.