You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #4726 and #4720 there was an assumption made based upon the jdk implementation that canceling the returned future from buildAsync or consumeBytes would close the the underlying resource if it occurred before the result were delivered. However our intervening logic means that we're dealing with a downstream future that is canceled - the upstream will still complete normally and could leak the connection. This will only happen in cases where the user manually closes something like a watch or a port forward before it initially completes.
The text was updated successfully, but these errors were encountered:
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jan 4, 2023
Related to #4726 and #4720 there was an assumption made based upon the jdk implementation that canceling the returned future from buildAsync or consumeBytes would close the the underlying resource if it occurred before the result were delivered. However our intervening logic means that we're dealing with a downstream future that is canceled - the upstream will still complete normally and could leak the connection. This will only happen in cases where the user manually closes something like a watch or a port forward before it initially completes.
The text was updated successfully, but these errors were encountered: