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.

Sign up for GitHub

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

Jump to bottom

wasm client issues on main #302

Closed

ecton opened this issue Jun 21, 2023 · 0 comments

Labels

Member

ecton commented Jun 21, 2023

The wasm client on the main branch has two issues:

After Client should have configurable timeout options #297, the client no longer works. The wasm timer dependency for handling timeouts caused the wasm app to not launch due to relying on some API that isn't supported. This needs to be replaced.
Apparently wasm subprotocols cannot have slashes.

After disabling the timeout code in wasm and changing the subprotocol to something different, the wasm client works again.

I want to look into when I last changed the subprotocol to determine if 0.4 had the same subprotocol, or maybe it didn't use the subprotocol yet.

ecton added bug networking labels

ecton closed this as completed in

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment