[release/23.7] Revert notify listeners #16425
Open
+0
−3
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.

WOOMOB-1835
Description
This is a rollback of #16350 for the
23.7release.In last minute before 23.7 rollout we discovered a crash that was happening for our results controllers. The first thing that came to my mind was a tweak to actualize the fetched object collection after a predicate / sorting change: Results controller: Notify listeners of changes when updating predicate and sort descriptors That's exactly the place where we touched the
ResultsControllerbehaviour. So let's revert it and revisit as a new task.Check out the WOOMOB-1835 for crash log reference.
Test Steps
N/A - Wasn't ever able to reproduce on my side.
RELEASE-NOTES.txtif necessary.