You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A deadlock issue was discovered in the @wordpress/data package when using resolveSelect on a selector/resolver pair implementing isFulfilled.
This failed test run from before adding the fix demonstrates the issue.
How?
The concept is to dispatch finishResolution to the metadata store when resolver.isFulfilled is true. This adds the correct state to the store, allowing resolution of the promises in mapResolveSelector and mapSuspendSelector.
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.
If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
What?
Add dispatch of
finishResolutionwhen a resolver'sisFulfilledcallback is true in the@wordpress/datapackage.Fixes #70805.
Why?
A deadlock issue was discovered in the
@wordpress/datapackage when usingresolveSelecton a selector/resolver pair implementingisFulfilled.This failed test run from before adding the fix demonstrates the issue.
How?
The concept is to dispatch
finishResolutionto the metadata store whenresolver.isFulfilledistrue. This adds the correct state to the store, allowing resolution of the promises inmapResolveSelectorandmapSuspendSelector.