-
Notifications
You must be signed in to change notification settings - Fork 46
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
Anywidget based widget exceeds MAX_OUTPUT_BYTES in marimo for no obvious reason #809
Comments
I just tried the link you shared, and it seems to be working. I see a regular count output when running the provided code and no indication of
It shouldn't. marimo's anywidget integration (to my understanding) correctly syncs data. As an aside, make sure to wrap your anywidgets in marimo with |
I refactored my widget around this so I'm not longer affected. But the behavior definitely exists from my testing. Did you make any code changes? A documentation update might be helpful. |
As mentioned, I do not see I am happy to reopen with more information and a minimum reproducible example. |
Ugh. I just tried to reproduce and I can't. I'm sorry. I swear I was seeing that example throw the MAX_OUTPUT_BYTES error. |
All good. Sorry for closing without an additional comment. Please let me know if it comes up again and you can reproduce. |
Describe the bug
I have a widget that is throwing errors in Marimo, based on "Your output is too large". In my widget I store a large dataframe in a trait that should not be serialized to the frontend (I have separate ways of sending dataframe state).
Why would a trait without
.tag(sync=True)
result in the output size increasing?Is there a way around this?
Reproduction
Logs
System Info
Severity
annoyance
The text was updated successfully, but these errors were encountered: