Fix the proxy command not detecting that the stream had closed remotely #799
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
This PR fixes an issue where a database client would hang despite the stream connection being closed.
Why?
This can happen when for example the proxy server has an error connecting to the target database. The proxy will log an error and close the stream, however Granted was not able to detect that the stream was closed and so it did not close its own connection to the database client.
How did you test it?
Tested locally by simulating database connection errors , the mysql client now reports a failure to connect instead of just hanging.
Potential risks
Is patch release candidate?
yes
Link to relevant docs PRs