Open ewagner70 opened 1 month ago
Hi @ewagner70 , thanks for your feedback.
I will try to reproduce this bug in databricks and find out the cause.
The size of pygwalker's HTML is around 19MB, which seems to have triggered the limitation of Databricks ipywidgets:
https://docs.databricks.com/en/notebooks/notebook-limitations.html#ipywidgets
The maximum message payload size for an ipywidget is 5 MB. Widgets that use images or large text data may not be properly rendered.
I am looking for a solution, and this may take some time.
The size of pygwalker's HTML is around 19MB, which seems to have triggered the limitation of Databricks ipywidgets:
https://docs.databricks.com/en/notebooks/notebook-limitations.html#ipywidgets
The maximum message payload size for an ipywidget is 5 MB. Widgets that use images or large text data may not be properly rendered.
I am looking for a solution, and this may take some time.
thank you for the update, @longxiaofei.
@ewagner70
@ewagner70
- interesting, I need to continue investigating this issue.
- This is related to the sandbox environment of databricks. In local jupyter, network requests can be processed very simply, but in a third-party online notebook, it is very troublesome to be compatible with this kind of network forwarding.
other widgets work (mitosheet, etc.) and don't seem to have any issue? Did you do something special with pygwalker? I can see that POST method is "not allowed" for whatever reason (maybe switch to GET to avoid that?)
Describe the bug pygwalker widget doose not get rendered in databricks. Only
Loading the widget is using longer than expected. We suggest the following ...
To Reproduce Steps to reproduce the behavior: open databricks noteook and insert the following code:
Expected behavior pyg.walk gets rendered as expected.
Screenshots here is the console output
Versions
Additional context