Fix the handling of removing disconnected streams to avoid a panic when multiple streams disconnect from the sdkserver #3668
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 type of PR is this?
/kind bug
What this PR does / Why we need it: Fixes a runtime panic when multiple streams disconnect from the sdkserver. This happens when a game server creates more than one watch and then closes them all at the same time. Normally, watches last for the lifetime of a game server, but if a game server intentionally disconnects watches and/or expects to be able to exit and restart (which implicitly disconnects the watches) then we hit this edge case.
Which issue(s) this PR fixes:
Closes #3640
Special notes for your reviewer: I tested this fix two ways: