Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Rendering is broken inside Databricks with DBR 11.x and higher - potential fix included
See original GitHub issueHello,
lets-plot used to work on Databricks with DBR 10.x (cluster version) and lower and we have customers who love and use it.
However, with DBR 11.x the auto-renderer breaks because it detects the wrong display type.
To fix this, customers have to explicitly do LetsPlot.setup_html(isolated_frame=True) because isolated_frame is auto-detected to be False. IMO most likely as part of _detect_isolated_frame.
Databricks can be detected e.g. via "databricks" in str(os.environ) which might be added to https://github1s.com/JetBrains/lets-plot/blob/HEAD/python-package/lets_plot/frontend_context/_html_contexts.py#L68-L69 or similar.
What do you think?
Issue Analytics
- State:
- Created a year ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@fwetdb I’ve pushed your proposal to master : https://github.com/JetBrains/lets-plot/commit/429e19aa541719b562c3f143f1387850cccad2c2
Luckily we are expecting the next release in few days so the fix is coming really soon.
Hi @alshan Thank you for the reach out and the fast release. I verified that the fix worked as intended.