Re: Podling Report Reminder - August 2018

HI, Yes it does take it seriously. If a report is not signed off, it's normally asked that the podling report again next month. I did have you down as reporting again this month (and that report is due in a day), but for some reason the email reminders don't seem to have reached your list.

Re: Call for fixes for Airflow 1.10.1

Also please add the following fixes: - https://issues.apache.org/jira/browse/AIRFLOW-2763 (Add check to validate worker connectivity to metadata) - https://issues.apache.org/jira/browse/AIRFLOW-1874 (use_legacy_sql added to BigQueryCheck operators) -

Re: Call for fixes for Airflow 1.10.1

Ash, thanks for picking this up! Maybe add this one: https://github.com/apache/incubator-airflow/pull/3804 https://issues.apache.org/jira/browse/AIRFLOW-2866 Cheers, Fokko Op ma 3 sep. 2018 om 14:47 schreef Deng Xiaodong : > Hi Ash, > > JIRA ticket 2922

Re: Apache Spark Interfering with Airflow Jira/PRs ??

On Mon, Sep 3, 2018 at 3:39 AM Ash Berlin-Taylor wrote: > Irrespective of the mis-configuration (Spark vs Airflow, bug causing loop > etc.) is it possible to do the action that is triggering the new email? We > already have Github creating some comments in Jira (which result in an > email) and

Re: Add git tag for 1.10

Aha so it is my mistake, apologies. On Mon, Sep 3, 2018 at 1:59 PM, Ash Berlin-Taylor wrote: > It is above the heading of Airflow 1.10, i.e. in the Airflow Master > section already. > > -ash > > > On 3 Sep 2018, at 13:53, Robin Edwards wrote: > > > > I am not sure if anyone's aware of this,

Re: Add git tag for 1.10

It is above the heading of Airflow 1.10, i.e. in the Airflow Master section already. -ash > On 3 Sep 2018, at 13:53, Robin Edwards wrote: > > I am not sure if anyone's aware of this, the 1.10.0 tag and the PyPi upload > dont contain the 'BashTaskRunner' -> 'StandardTaskRunner' change. > >

Re: Add git tag for 1.10

I’m not sure what you think is off? The change is only in master not in 1.10. If you are reading the docs for updating to master then you are using the wrong docs if you are upgrading to 1.10. B. Verstuurd vanaf mijn iPad > Op 3 sep. 2018 om 14:53 heeft Robin Edwards het volgende >

Re: Add git tag for 1.10

I am not sure if anyone's aware of this, the 1.10.0 tag and the PyPi upload dont contain the 'BashTaskRunner' -> 'StandardTaskRunner' change. The docs in master do https://github.com/apache/incubator-airflow/blob/master/UPDATING.md (They don't in the 1.10.0 tag) If this is intentional and the

Re: Call for fixes for Airflow 1.10.1

Hi Ash, JIRA ticket 2922 was fixed together with *2921* in PR 3773 (which was already listed by you). Understand that it may be included in 1.10.1 automatically if this PR is included, but

Call for fixes for Airflow 1.10.1

Hi everyone, I'm starting the process of gathering fixes for a 1.10.1. So far the list of issues I have that we should pull in are https://issues.apache.org/jira/issues/?jql=project%20%3D%20AIRFLOW%20AND%20fixVersion%20%3D%201.10.1%20ORDER%20BY%20key%20ASC (reproduces below) I will start

Re: Apache Spark Interfering with Airflow Jira/PRs ??

Irrespective of the mis-configuration (Spark vs Airflow, bug causing loop etc.) is it possible to do the action that is triggering the new email? We already have Github creating some comments in Jira (which result in an email) and would like to keep the email volume down. Might be worth

Security issue being ignored?

Hi, I noticed you opened a disccusion about the neccesity of Gitter... I think the main problem is that unlike other open source projects with Airflow no one is monitoring the Jira. So people tend to report many stuff on the Gitter to get assistance. Sometimes answers are given but no one answer