Issue: https://github.com/apache/airflow/issues/27135
airflow db upgrade returns below error:
Traceback (most recent call last):
File "/Users/panksingh/Documents/workspace/airflow-plugins/venv/bin/airflow",
line 8, in
sys.exit(main())
File
BTW. I spoke To Andrey (AKA @Taragolis) and I think (and Andrey agrees) he
would be a great member of the Triage team.
PR: https://github.com/apache/airflow/pull/27278
On Tue, Oct 25, 2022 at 9:04 PM Jarek Potiuk wrote:
> > Losing these folks is a bad experience for them but also for us
> Losing these folks is a bad experience for them but also for us because we
> lost perhaps a great future contributor/committer/triager.
Cannot agree more - that this is what I would really like to avoid !
Pretty much Every time we lose someone passionate who loves our
product and would be a
>
> 3. I am also getting a true sense of just how overwhelming the influx of
> Issues, PRs and Discussions is. I have come across several folks who
> submitted PRs and never got feedback and then left the community. Losing
> these folks is a bad experience for them but also for us because we lost
Thanks Jarek for the extra context and additions to the Traiging rst!
An update from my end as a new Triage member:
For the past few weeks I have looked at every single notification from Airflow
Github and it has been a very informative learning experience.
1. Beyond tagging and updating
Yep. I think legally it's pretty much settled indeed. It's now just the
question on whether you want to choose the path where you manage your
provider or not and put some convincing arguments for it here :D
J.
On Wed, Oct 19, 2022 at 8:48 PM David Sanchez Plaza
wrote:
> Dear all,
>
>
>
>
Hey everyone,
I think with the recent addition of Denis and Niko to the triage team we
already see some good signs that we should likely make the triage team
stronger and also incentivised to help :).
I think this is instrumental to be more welcoming for our community to
respond quicker to
