prha

I'd feel a whole lot better about this change (especially with the run key tag change) if we added some tests.

Specifically, using list values for tags in combination with non-list values for tags.

This is separate.... in case we want to change the stored run tags to remove the serverless account id from the arn/cluster.

We have data migrations which will run when users run `dagster instance migrate`. We can just put something in the release notes saying that if they see something odd when...

I actually prefer `Composite` to `CrossProduct` (which maybe feels too mathy). If we wanted to distinguish between the cross-product and the sum (which I think would be pretty rare), I...

some naming alternatives: * MultiPartitionsDef * MultidimensionalPartitionsDef * CompoundPartitionsDef

I think this has been replaced with more standard joins/intersections starting in `1.0.10`.

@gibsondan made the excellent observation that as soon as a slot opens up, all of the runs blocked by that key will suddenly dequeue. We'll probably have to do something...

it doesn't really matter whether we do the bulk of the calculation at enqueue or dequeue time... the granularity is the annoying thing here. The solution I've been playing around...

Okay, I updated this with the following changes: We tag each run upon submission with a map of step key => concurrency key and a list of all the root...