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

Azure Databricks Compatability #229

Open
ayjayt opened this issue Nov 18, 2024 · 1 comment
Open

Azure Databricks Compatability #229

ayjayt opened this issue Nov 18, 2024 · 1 comment
Assignees
Labels
active TNG related to next-generation architecture

Comments

@ayjayt
Copy link
Collaborator

ayjayt commented Nov 18, 2024

Not sure how to circumvent this new requirement in a serverless compute on Azure Databricks...

It seems chromium cannot be accessed in those conditions and will always end up in error if trying to save plotly plots as static images.

Originally posted by @pdmkdz in #224 (comment)

Hi @pdmkdz,

I will investigate this and report back. For now, if its really impossible to pull in chrome, you can probably downgrade Kaleido to a v0.1.xx or maybe a v0.2.xx- but I will have a better answer for you this week.

@ayjayt ayjayt self-assigned this Nov 18, 2024
@ayjayt ayjayt added TNG related to next-generation architecture active labels Nov 18, 2024
@pdmkdz
Copy link

pdmkdz commented Nov 19, 2024

Thanks for opening this, I was about to open an issue, perfect timing.
I am pinning to %pip install kaleido==0.2.1 for the time being, and works fine.
I contacted the Databricks reps to see if we can circumvent these issues and have the headless browser, but my attempts have been pointless when running from a notebook browser using a serverless compute.
So to be able to run it in Databricks gotta be self contained like in the past.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
active TNG related to next-generation architecture
Projects
None yet
Development

No branches or pull requests

2 participants