-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
mocknet newStream notification issue #31
Labels
exp/wizard
Extensive knowledge (implications, ramifications) required
help wanted
Seeking public contribution on this issue
kind/bug
A bug in existing code (including security flaws)
Comments
ghost
added
status/deferred
Conscious decision to pause or backlog
and removed
status/deferred
Conscious decision to pause or backlog
labels
Nov 12, 2016
daviddias
added
kind/bug
A bug in existing code (including security flaws)
exp/wizard
Extensive knowledge (implications, ramifications) required
labels
Aug 19, 2017
Is this still the case? This looks fixed. |
Let's close this due to age and lack of activity. |
marten-seemann
pushed a commit
that referenced
this issue
Apr 22, 2022
update to the latest quic-go, gx publish
marten-seemann
added a commit
that referenced
this issue
Apr 22, 2022
update go-yamux to v2.0.0, use context passed to OpenStream
marten-seemann
added a commit
that referenced
this issue
May 18, 2022
pass contexts to OpenStream in tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
exp/wizard
Extensive knowledge (implications, ramifications) required
help wanted
Seeking public contribution on this issue
kind/bug
A bug in existing code (including security flaws)
When opening a new stream using the mocknet (
p2p/net/mock
) the connection handler doesnt get called until a write actually occurs. I beleive this is a bug.The text was updated successfully, but these errors were encountered: