Fix module hotswapping for connected clients #3159
Merged
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.
The
Cloneimpl forClientConnectionwould create an independentinstance that could not observe module hotswapping. This would result in
methods called on a replaced
ModuleHostto fail, because that hostexited already.
Fix by reading the
ModuleHostfrom the watch channel directly, insteadof maintaining a redundant copy.
Also fix
watch_module_hostto properly mark the current module host asseen.
Expected complexity level and risk
2
Testing