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

Timeouts don't work on wasm32 #13

Open
simbleau opened this issue Jul 5, 2024 · 0 comments
Open

Timeouts don't work on wasm32 #13

simbleau opened this issue Jul 5, 2024 · 0 comments

Comments

@simbleau
Copy link
Member

simbleau commented Jul 5, 2024

G'ah. Just noticed timeouts are sticky on wasm32. An error around condvar.wait not supported, which is expected.

I'm not sure what solutions there could be for timeouts. Perhaps just turning off timeout methods on wasm32 is good enough.

We can add a .setTimeout to the browser to set a flag like "timed_out = true", but the only way for the task runner to be notified of the timeout is to spin-lock until it's timed out, which isn't asynchronous behavior. This will require some thought.

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

No branches or pull requests

1 participant