Sean Mackesey

* **#21976** 👈 * **#22249** * **#22245** * `master` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @smackesey and the rest of your teammates...

@prha I think I'm going to need to add some more tests but I'd like your take on the approach here. The storage implementation is in the linked internal companion...

You can also use redundant aliases instead of `__all__` to mark imported symbols as (public) exported. Cleaner and more maintainable IMO. That's what we do in [Dagster](https://github.com/dagster-io/dagster/blob/master/python_modules/dagster/dagster/__init__.py#L153-L163) to prevent these...

The plan here is to proceed post-1.8: we'll show unsynced status of the latest partition for time-partitioned assets while retaining the status quo for non-time-partitioned assets. >cc @smackesey is this...

Heads up that you are being heard and we are discussing potential solutions. Just to provide some more context-- the reason we don't currently compute and display the per-partition sync...

>You guys are the experts but I know the sync status of each partition is computed and the UI is already fully aware of which partitions are outdated. You can...

>If you want to do something about expensive backfills in general, I strongly, in the strongest possible terms, recommend tag_concurrency_limits be respected when set at the asset or resource level....

@ion-elgreco >are these always calculated when a user refreshes? If so, why not cache this info in a redis instance and make it possible that the cache gets refreshed automatically...

* **#22569** 👈 * **#22682** * **#22677** * `master` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @smackesey and the rest of your teammates...

* **#22750** 👈 * `master` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @smackesey and the rest of your teammates on Graphite