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

Closed stream is polled causing debug assertion to fail for WebTransport in wasm #5618

Open
fl0rek opened this issue Oct 3, 2024 · 0 comments

Comments

@fl0rek
Copy link

fl0rek commented Oct 3, 2024

Summary

I'm connecting to a peer over WebTransport in a browser. When running release builds app is behaving correctly. Debug builds (including tests) on the other hand fail shortly after connecting. In browser console I see panic, which seems to be coming from this debug_assert. Additionally when I change the debug_assert to panic, release builds also fail.
Rest of the libp2p seems to continue in a degraded state, as I see logs from e.g. running behaviours.

Expected behavior

I expected debug builds to work same as release, where the behaviour is able to correctly send the request and get a response.

Actual behavior

Behaviour seems to hang indefinitely, I'm guessing it's waiting to send/flush

Relevant log output

No response

Possible Solution

I guess removing the assert or making sure that closed stream isn't polled would fix it, but I don't know enough about libp2p to know which would be the correct solution.

Version

tag: v0.54.1

Would you like to work on fixing this bug ?

Yes

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