-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
event_forward_extremities are not correctly cleared by persistence of successor events #8913
Comments
(in the above example, I would expect to end up with |
Closing in favor of #6607 |
I'm not convinced they are quite the same. #6607 is specific to de-outliering; this doesn't involve outliers. That said, both issues are pretty old; it's entirely possible that one or both have been fixed. |
Agreed!
Is this still true in the light of the dummy events created by #5884 ? |
Aside: isn't it enough to see a single ancestor of A for A to no longer be considered an extremity? |
No. Nevertheless dummy events are a bit of a kludge and there could be fewer of them if we didn't create spurious forward extremities.
I'm not really following. No number of ancestors of A changes whether A is a forward extremity. Maybe you mean backward extremities but they are different anyway. |
I was writing nonsense. What I should have written is: Isn't it enough to see a single |
ah. Then yes. |
Suppose:
A <- B <- ... <- C
, where C is a regular event, which references B in its state.event_forward_extremity
of A.Empirically:
event_forward_extremities
of A and CWe have all the successors for A we should ever expect to receive, so I assert that it should no longer be considered an extremity. In particular, there is no way it will ever cease to be a forward extremity, so it contributes to the accumulation of forward extremities (cf #1760).
The text was updated successfully, but these errors were encountered: