-
Notifications
You must be signed in to change notification settings - Fork 898
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
Do not rely on the asset pipeline when calling backend PDF generation #18236
Conversation
Checked commit skateman@1c1bd95 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@miq-bot add_label blocker |
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.
LGTM :)
Looks like AssetWriter
is no longer relevant now that ImageEncodeHelper
is gone and the css only includes external fonts.
@h-kataria or @martinpovolny can you merge please? |
Do not rely on the asset pipeline when calling backend PDF generation (cherry picked from commit ce0cd61) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1650057
Hammer backport details:
|
There were some extra asset pipeline-related calls even after #18226 in the backend PDF generation code that caused problems in some special cases. I have no idea why would we call the asset_path on a file twice, but now it's not called even once.
@miq-bot add_label gaprindashvili/no, hammer/yes, bug
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1650057