Kevin J Dolan

I would like to second this. There is the abstract base class PartitionsDefinition, which can easily be extended by a user, but this will throw the error: `dagster._core.errors.DagsterInvalidDefinitionError: Only static...

An alternative for my particular use-case would be able to chain multiple partition defs together such that all combinations are produced.

Note: included in the test cases, similar behavior is observed when you have a task that calls `self.replace()` with a group (though sometimes it is slightly different), as below: ```python...

Including an updates test suite here to include some test with chords (as I understand groups are converted to chords behind the scenes when unrolling a chain): [celery_bug_report_2.zip](https://github.com/celery/celery/files/13893001/celery_bug_report_2.zip) If we...

I've observed that top-level normal tasks that fail seem to consistently propagate errors, which leads to a few workarounds. Attaching updated test suite to demonstrate the workarounds: [celery_bug_report_3.zip](https://github.com/celery/celery/files/13893862/celery_bug_report_3.zip) If we...

Finally, a more abstracted workaround is to create a couple dummy tasks that wrap the call to the desired task in a `safe_call` task that catches and returns exceptions, and...

Wow that was fast! Excited to get rid of my workaround!

@Nusnus: FYI -- I ran my test suite on 5.4.0rc0, and while it did fix a couple of the tests, many are still failing, so I believe the core issue...

@Nusnus Expected behavior for that snippet would be to raise the exception MockException shortly after the failing task is run -- it should bubble up. This is as opposed to...

@Nusnus this issue is still present -- should I create a separate bug report?