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

Fix idle timeouts for websockets and streaming connections in 3.8.x #11004

Open
wants to merge 1 commit into
base: 3.8.x
Choose a base branch
from

Conversation

yawkat
Copy link
Member

@yawkat yawkat commented Jul 23, 2024

Before this patch, the configured timeout would be applied for the read, write and combined streams. That means that if data was only sent in one direction on the connection, the timeout would trigger and the connection would close.

This patch changes the timeout to only apply when no data is sent in either direction.

Before this patch, the configured timeout would be applied for the read, write *and* combined streams. That means that if data was only sent in one direction on the connection, the timeout would trigger and the connection would close.

This patch changes the timeout to only apply when no data is sent in either direction.
@yawkat yawkat added the type: bug Something isn't working label Jul 23, 2024
@yawkat yawkat requested a review from graemerocher July 23, 2024 06:54
@yawkat
Copy link
Member Author

yawkat commented Jul 23, 2024

@melix so, what do we do about PRs like this, now that jcenter is broken? Can't build or test

@melix
Copy link
Contributor

melix commented Jul 23, 2024

3.8.x ? wow. I guess it will require a fair amount of changes to fix the build :/

@graemerocher
Copy link
Contributor

do we need the PR given the workaround is to set 0 to the timeout?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants