fix: Network controller race condition after state update #5122
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.
Explanation
Fixes a race condition where:
stateChange
subscription callback, callgetNetworkConfigurationByNetworkClientId
on the new endpoint.This occurs because the
network client id -> network configuration
map was being built after the state update, so it was not ready at the time of thestateChange
event.The fix involves moving this map building inside the state update, so that its built by the time
stateChange
fires. But also requires deep cloning the state before building the map from it. Otherwise we getCannot perform 'get' on a proxy that has been revoked
when referencing the ephemeralstate
lambda.References
Changelog
@metamask/network-controller
getNetworkConfigurationByNetworkClientId
in response to astateChange
event adding a new endpoint to a network.Checklist