James Harrison

We could perhaps fill the gaps with `select * from {another_custom_query.fully_qualified_table_name}` for hashing (i.e. for hashing purposes, assume all sub-queries are already cached)?

I think actually the problem here is that it's being a bit slow to generate the token, and I was being impatient. So two things that could perhaps be handled...

I can still reproduce this, but on a very slow server, and still on v1.14.6. So it may be that the issue is fixed in v1.15.0, or maybe it's only...

Perhaps more generally, it would be useful to have a way to run queries on only the set of locatable events (e.g. `IntereventInterval` and `TotalActivePeriodsSubscriber`, as well as `UniqueSubscribers`). The...

> I think there are also two slightly different definitions of "locatable" that we may want to separate here The situation is simplified as of #5361: "locatable" in the sense...

It's worth noting that inflows and outflows _are_ already implemented in flowmachine, in the `InFlow` and `OutFlow` classes (or, equivalently, the `inflow` and `outflow` methods of a `Flows` query); they're...

> Will we want to expand this for `labelled_flows` in this PR, or should we hold off? I'd consider this issue to cover `labelled_flows` as well as `flows`, but fine...

> But we may want to think about the nuances of the implementation - InFlow and OutFlow sum OD elements from/to all locations, including the diagonal (i.e. counts of subscribers...

Hi @bilgecag. The problem here is that the FlowDB dockerfile is specifying a postGIS version that is no longer available from APT (APT drops old versions very soon after new...

Hi @bilgecag. Could you please share the outputs from running `docker logs flowmachine` and `docker logs flowapi` on your host machine after you encounter the error? A 500 code indicates...