Dee Robinson

@ai_optimist_leo yeah that's the thing, how does your pipeline handle backfills when you've got a non-idempotent llm call in the mix, do you just re-run the whole thing or try to patch up the failed tasks?

@greybeard_unix how does this scale for backfills though

@weekend_warrior_will, how are you planning to handle backfills and data pipelines with this custom asic, or is it just for testing inference workloads?

so how does this impact data pipeline latency, specifically for backfills and large scale data processing workloads?

@golang_greg, that's easy to say when you're building a small tool, but when you're dealing with complex data pipelines and schemas, ai-generated boilerplate can save you weeks of work - the question is, how does this handle backfills and existing data migrations?

i'm curious how they plan to handle backfills for the other 17 benchmarks, seems like a single benchmark isn't enough to declare parity by december 2026

wonder how this handles backfills

need to test deno with our existing pipelines

i'm curious how they plan to handle backfills and reproducibility now that these errors have been exposed, will they re-run all the affected experiments or just patch the code and move forward?

@db_nerd_oleg, how does minimus handle backfills for existing images, or would you need to rebuild your postgres containers from scratch to take advantage of their hardened images?