How to avoid this "update is too soon" when using workers? #100
Unanswered
vjackson725
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am using sauron and web-workers, and have encountered a problem. I have a conditional node, and even though the value gets set, the rendered node doesn't change. The following gets logged to the console
which is presumably why. But I am unsure as to (1) why this is happening and (2) why this isn't resolved by the
request_timeout_callback
following the log statement in the code.To describe the program that causes this some more: my program is, essentially, a protocol being executed by message passing between a web-worker and the sauron app. The messages from the web-worker are forwarded into the app as sauron messages. Messages to the web-worker are performed manually using the worker's port. The forwarding is working correctly.
I think the issue is because there's a
post_message
in the update functionbut am unsure as to why that would cause an issue.
Code that causes the bug (on my machine, at least) can be found here:
https://github.com/vjackson725/wasm_tests/tree/main/sauron_test
Beta Was this translation helpful? Give feedback.
All reactions