Idiom

Here is an example of what this looks like, when running multiple times and continuing to increment. ``` [ppss.lake configuration run #1] ppss.st_ts = Jan-01-2023, ppss.fin_ts = Feb-01-2023 [ppss.lake configuration...

We have various retries added and improved this overall. I have closed this ticket and have updated the core issue.

I agree in general that all services (including different agents/bots) would benefit from having a lake that's just up-to-date. And having a process that's solely-responsible for doing this is the...

DuckDB only lets you have 1 writer process at a time that holds the db writer connection. Within this, you can then have multiple threads/operating on it. So, for the...

Alternatively, expand gql_data_factory, such that it can handle: 1. Post-fetch processing of bronze tables 2. Processing of silver tables (enrich, aggregate for time-series analysis) 3. Processing of gold tables (metrics,...

### Motivation To prevent re-fetching data from subgraph we're going to maintain our own view of the final state of each prediction. This means that we'll be joining to calculate...

I'm going to close this ticket, too broad. We've delivered the first implementation.

We want properties from all 4 tables: 1. slots (info about the slot, feed, etc..) 2. predictions (all predictions submitted and their final results) 3. truevals (what was the final...

### Notes Overall, we have low conviction around problems/improvements as a result of this update. This is therefore low priority.

We can improve the fetch step by returning more of the expected records from predictPredictions. By doing this, we can reduce the need to fetch the predictPayouts table. We would...