Bug (IN-42182) [1.0.10] Keep running change filter at owner predicted ghost

I didn't check the repro yet.
But as a remainder: as soon as you have a query that is not readonly or retrieve a component in a job with non-read-only access, no matter what you do with it, its value is considered changed, even though it is not.

The change filter does not consider or check that component data/fields is actually modified at all (in general). And because it is owner predicted, I assume the owner client modify the ghost, so that should be expected somehow.
But remote clients should see it as interpolated ghost, so it should behave like them. Is the value changed seen on the "inteporlated" ghost or the predicted ghost?

 

Indeed that can happen for many reason. And I think the one reason for that are partial ticks.
We restore the state of the components to that last full tick when doing the partial updates; And this invalidate the change filter.
We can add some extra logic to handle that, but it indeed cause some performance costs.