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

[Bug?]: When triggering a Server Action -> Nested Cache (Server Resource) triggers infinite loop #1666

Closed
2 tasks done
MauruschatM opened this issue Oct 28, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@MauruschatM
Copy link

Duplicates

  • I have searched the existing issues

Latest version

  • I have tested the latest version

Current behavior 😯

No response

Expected behavior 🤔

No response

Steps to reproduce 🕹

Steps:

  1. Create two async server cache function and one server action
  2. In the page, load the one cache function and a Component-2
  3. In Component-2 load the other cache function (with createAsync)
  4. In Component-2 create a button that triggers the action

Context 🔦

No response

Your environment 🌎

No response

@MauruschatM MauruschatM added the bug Something isn't working label Oct 28, 2024
@MauruschatM
Copy link
Author

I also have tried using Suspense nowhere and everywhere. It works when having no Suspense at the Root-App Level only with hot refresh. When reloading the page you obviously get the hydration error.

@MauruschatM
Copy link
Author

Important code snippets in the solidjs discord: https://discord.com/channels/722131463138705510/1298351918749454356

@MauruschatM
Copy link
Author

Ok sorry. I copied my project and broken down every line of code. The issue is somehow related to a different component which has some kind of reactivity, but nothing to do with this logic above. Really weird.

If anyone has this issue in the future: Never use server stuff in any kind of reactivity, even if it works in the beginning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant