Sean Mackesey

I'm a big fan of the direction this is going. I need more time to pull all my thoughts together, but two questions come to mind. First, this RFC is...

Thanks for the report @JasperHG90. cc @clairelin135 (feel free to punt to someone more appropriate) have you been working on backfills recently?

Thanks for catching my mistake, I believe this was already fixed here though: https://github.com/dagster-io/dagster/pull/21731

* **#20238** 👈 * **#12115** * **#10983** : 1 other dependent PR ([#12112](https://github.com/dagster-io/dagster/pull/12112) ) * **#12102** * `master` This stack of pull requests is managed by Graphite. Learn more about...

Also, why `AssetSpec` instead of `AssetNode` (I understand we're not locked in though)?

I think we will want to transition to `AssetNode` later (and convert specs to nodes in the constructor) so that our internals are maximally decoupled from public `AssetSpec` but I...

Something to note-- single-run backfills are currently poorly named because the way they work is a single-run _per continuous slice of partitions_, rather than a single run for all selected...

Update: This should be fixed with week's release.

https://github.com/dagster-io/dagster/pull/21259 Is the main one, there were several bugfix ones on top of it.

Has anyone in this thread updated to latest Dagster and confirmed that the issue is resolved?