-
Notifications
You must be signed in to change notification settings - Fork 39
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
Kaleido 0.4 image export fails #223
Comments
I also have a daily GHA failing this AM, due to picking up Kaleido 0.4.1. I've "fixed" it by pinning to 0.2.1.
Apologies if this should be its own issue, the error msg looks slightly similar to the last one above (something is |
I also faced
in GitLab CI with versions With
I had to downgrade to |
A lot going on here! For the first error, Kaleido now requires that chrome is installed separately. I'm going to push a fix for the second error- but basically that error is that there is no chrome installed, although it shouldn't present like that. |
I also fixed it by pinning, like a already do for a long time for Windows (see #110):
|
0.4.1 contains an issue that breaks the tests: plotly/Kaleido#223
* Fix all mypy issues * Fix kaleido version 0.4.1 contains an issue that breaks the tests: plotly/Kaleido#223 * Fix tests * Fix version limit
Hi everyone! If you're comfortable pinning a lower version of kaleido, that's fine- but keep in mind that chromium came with the older version and it is an older and less secure version of the browser. The browser is no longer shipped with the package (its too large), and you have to install it separately to use the newer versions of kaleido. tl;dr: please install chrome/ium separately |
This is showing up when installing Kaleido on Job Run in databricks without set version and simply doing fig.show() in plotly. |
I thought the whole point of kaleido was is that it doesn't need external dependencies, and simplifies image exports by embedding a headless browser binary. What changed? Is there a new announcement or release notes? And is there a way to keep my Python project independent of external dependencies if it relies on Plotly image export? |
The issue is that chromium was always built into kaleido, but its gotten too large to include in the package by pypi rules- although I think we'll end up talking with them to see if they'll allow it. The other option is to include an |
Thanks so much for detailed explanation! |
Hey,
just noticed some fails in my CICD that started occurring with the recent 0.4 version.
<0.4 works fine.
This is what i'm getting as error:
Python:
Fails for 3.9 to 3.12
System:
I also have a Gitlab CI running, where this error also occurs but in a different form (also started with 0.4, so i assume it's related):
The text was updated successfully, but these errors were encountered: