Skip to content
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

Add server context to suspense resolution #3552

Merged
merged 2 commits into from
Jan 13, 2025
Merged

Conversation

Houndie
Copy link
Contributor

@Houndie Houndie commented Jan 12, 2025

While this was done correctly in the streaming case, non-streaming suspense resolution didn't recieve the server context. This meant that anything that required the context after the point of suspension would find it missing.

This resolves #3500

While this was done correctly in the streaming case, non-streaming
suspense resolution didn't recieve the server context.  This meant that
anything that required the context after the point of suspension would
find it missing.
Copy link
Member

@ealmloff ealmloff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! We might be able to just wrap the whole spawn platform future in provide server context instead of setting it individually several times within the future

@jkelleyrtp jkelleyrtp merged commit d5a04c6 into DioxusLabs:main Jan 13, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug with context and server functions...context in _second_ called function not found.
3 participants