Closed nbauernfeind closed 1 year ago
This is because we're not ensuring that the result FilteredTable
checks the satisfaction of its filters before declaring itself satisfied.
We should make WhereFilter
implement NotificationQueue.Dependency
. In most cases they will not need anything special, but in the case of ClockFilter
it is not satisfied until the update graph is.
FilteredTable
should refer to its filters via addParentReference
instead of an array for referential integrity + management.
Or we could leave stuff mostly alone and just make sure ClockFilter is a NotificationQueue.Dependency that delegates to the UpdateGraph
for satisfaction.
Or we could change BaseTable.satisfied()
to always check that the UpdateGraph
is satisfied.
I then look at
t1
in the web UI and scrolled to the bottom. The UI keeps making newflatten
requests, which seems to be related.I have seen both of these: