Skip to content

Conversation

@GregDThomas
Copy link
Contributor

We've just started seeing this problem (though the ticket was raised over three years ago!)

This PR fixes it by using a future with an explicit timeout.

(I've got larger concerns over the age of the underlying SSH library that makes this necessary, but that's a larger change that needs considerably more effort!)

@GregDThomas GregDThomas mentioned this pull request Aug 19, 2025
@GregDThomas GregDThomas force-pushed the get-rpc-reply-hangs branch 2 times, most recently from 8de7769 to 0b4b66f Compare August 20, 2025 10:36
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