-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Document streaming: Maximum update depth exceeded #639
Comments
Agree, please fix. Before this is fixed the template is unusable. |
@athrael-soju It's two weeks old, so I intentionally re-raised the issue as a duplicate. |
Let me clone and verify, I'll self-close for you, thanks so much. |
@jeremyphilemon This is absolutely fixed, just tested deploy flow, really good work. #589 is the original issue. |
Thankyou @jeremyphilemon !! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reporting same issue as #589. Actually very hard to debug, can't tell where the loop is coming from or how to break it. The stream gets passed from
useChat()
to<BlockStreamHandler>
and somewhere along the line it apparently loops.experimental_throttle
inuseChat
, you can avoid it somehow, or the layout doesn't jank - but then chunks are missed (which is confusing, I'd think that would just space the chunks out).It is a pretty big issue with the template, and the template/layout is not really stable until this is fixed. I've tried to debug it for a few days but ultimately would be fastest for original authors to find the leak. Aside from that, it's beautiful and I'm shocked this supports documents/canvas now, very helpful. I'm just streaming document output to regular message boxes for now to work around this.
cc @jeremyphilemon
The text was updated successfully, but these errors were encountered: