Fix the race condition during create initial connection #64
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.
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
atkube-forwarder/src/renderer/lib/k8s-port-forwarding-patch.js
Line 55 in c62fe44
processData
is called,ws
is created atkube-forwarder/src/renderer/lib/k8s-port-forwarding-patch.js
Line 29 in c62fe44
ws
.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.