Azure Databricks Compatability
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 498
- Forks
- 62
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 2
Description
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 https://github.com/plotly/Kaleido/issues/224#issuecomment-2484176831
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing static Plotly image export in Azure Databricks serverless compute and tracing where Kaleido requires Chromium. The payload names no files or tests, so locate the Chromium and static-image export entry points first. Done means the Azure Databricks compatibility behavior is understood and a supported outcome is documented or implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100