Closed madogiwa closed 3 years ago
I think that this PR is likely to resolve issue #63.
Below is an example sequence to describe the problem fixed by the PR.
await createWS
processData
ws
I don't know the specific reason, but sending data from a different WS along the way seems to cause TLS issues.
I think that this PR is likely to resolve issue #63.
Below is an example sequence to describe the problem fixed by the PR.
await createWS
at https://github.com/pixel-point/kube-forwarder/blob/c62fe441d9e994828efe544b6be6ba34d01ad40d/src/renderer/lib/k8s-port-forwarding-patch.js#L55 and wait for it to finish.processData
is called,ws
is created at https://github.com/pixel-point/kube-forwarder/blob/c62fe441d9e994828efe544b6be6ba34d01ad40d/src/renderer/lib/k8s-port-forwarding-patch.js#L29 and sent data usingws
.await createWS
is finished,ws
is overwritten to a new connection.processData
is called again, the data is sent using the newws
.I don't know the specific reason, but sending data from a different WS along the way seems to cause TLS issues.