Attempt to leverage standalone headless chrome binary #207110
Draft
+175
−467
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eokoneyo
added
release_note:skip
|
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
|
Given the progression of the conversation in the linked issue above, maybe it's not worth pursing this approach till the issue is resolved, alternatively we could stick to this approach for all other platforms and continue with building just for ARM 🤷🏾 , @tsullivan wdyt? |
eokoneyo
added
the
Feature:Reporting:Framework
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR relates to https://github.com/elastic/kibana-team/issues/655#issuecomment-2593568117
In this PR, we attempt to leverage the standalone headless chrome binary provided by the chrome team for reporting in Kibana, in place of using the entirety of chrome in
darwinandwinplatforms, furthermore adopting this approach would imply that we don't need to build our own version of the headless chrome anymore.Giving this a try it works for the darwin platform, see
However for the linux platform the provided binary doesn't work for arm, see screenshot below
This is a known issue, see GoogleChromeLabs/chrome-for-testing#1, which sort of puts a pin in this idea :( of not having to building our our own variant for headless chrome.