Hi all! I just had a thought about reporting bugs.
Of course we don't expect everyone to jump in and send PRs fixing bugs, especially when the reported bug touches the core of Airflow and requires a lot of context to fix. If you can, one thing that can really help is to *provide a failing unit test along with your bug report*, in the form of a branch/PR in your fork. This failing unit test: * makes it crystal clear what your expectation are, in some cases bug reports are in fact misaligned expectations * allows a committer to jump in with a clear goal / deliverable to fix the unit test, without having to find a way to recreate the bug first, which can be really hard in some cases * prevents regressions as the [now fixed] unit test gets committed along with the new feature I know it's a lot more involved to do than just opening an issue, but if you really want a bug fixed that's probably the best way to go! Max
