Open david-boles opened 1 month ago
I'm having some trouble producing a minimal reproducible example, so I think there's more playing a role here, but it seems to be related to use_server_future
returning RenderError::Suspended
(and me propagating that back up) on the client. Just dropping the return value from use_server_future
makes this error go away. Although the initial return value from use_server_future
doesn't change between release and not-release.
Welp, this is odd. Adding:
tokio::time::sleep(Duration::from_millis(1000)).await;
To my #[server]
function being called through use_server_future
fixes it. Maybe I'm hitting some sort of race condition on the client?
I notice that that does delay the final part:
<div id="ds-0-r" hidden><!--node-id0-->root<!--#--></div><script>window.dx_hydrate([0], "...")</script></body>
</html>
Getting delivered and thus hydration starting.
Problem
Client-side panic when hydrating a release (not debug) fullstack build on 0.6.0-alpha.2:
Chrome:
Steps To Reproduce
Unsure; it doesn't happen in a new project. Will try to narrow down what's causing it in mine.
Expected behavior
No panic.
Environment: