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

Client-side timeouts #268

Merged
merged 4 commits into from
Jan 17, 2025
Merged

Client-side timeouts #268

merged 4 commits into from
Jan 17, 2025

Conversation

edsko
Copy link
Collaborator

@edsko edsko commented Jan 17, 2025

No description provided.

edsko added 2 commits January 17, 2025 13:46
The connection monitor is a thread we spawn for each RPC; it's job is to
monitor the connection and close the RPC if the entire connection is closed. In
order to prevent memory leaks, the thread also terminates when the RPC is
closed independent of the connection. However, we were waiting for termination
of the _outbound_ thread to determine if the RPC is closed; it's better to wait
for termination of the _inbound_ thread, because the outbound thread is
terminated when the client sends its final message, but at that point we might
still be waiting on further messages from the server.

This doesn't matter too much, but becomes important in the next commit.
edsko added 2 commits January 17, 2025 17:45
The problem is not that the client imposes a local timeout, this is per the
spec; the moment is that the server closes the connection in response to the
deadline but without sending the appropriate error.
@edsko edsko merged commit 17ae234 into main Jan 17, 2025
6 checks passed
@edsko edsko deleted the edsko/issue-221 branch January 17, 2025 16:55
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

Successfully merging this pull request may close these issues.

1 participant