-
Notifications
You must be signed in to change notification settings - Fork 3.6k
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Cannot pull closed port (One2OneBidi.in) #20944
Comments
I wonder if this is read / has not happened anymore since a while. |
Do we even have One2OneBidi? |
Yeah, but it's a Http internal stage |
Ah I thought it was removed completely at some point. |
So, what it does is protecting the user from streaming more responses than there are requests, not sure when this would happen so from that perspective it could maybe be removed. However it also is what enforces the "pipeliningLimit", so that further requests are backpressured if this limit is reached, if we remove it we'd have to introduce another stage that does that. :( I'll just see if I can fix the bug instead. |
I know what it does, I have worked with this beast before. I just thought we removed the protection altogether, but I see that we still need it. |
When running HTTP without fusing
The text was updated successfully, but these errors were encountered: