Re: [VOTE] Release Airflow 1.10.4 from RC5

+1 (non-binding) Tested the Airflow pool and it is working as expected. Chao-Han On Mon, Aug 5, 2019 at 1:09 PM Felix Uellendall wrote: > +1 (non-binding) > > Tested: > - running example dags on Sequential and LocalExecutor > - classic UI and RBAC UI (connections, variables, pools, xcom, logs)

Re: [VOTE] Release Airflow 1.10.4 from RC5

+1 (non-binding) Tested: - running example dags on Sequential and LocalExecutor - classic UI and RBAC UI (connections, variables, pools, xcom, logs) There is a small issue with the logs containing symbols for coloring instead of actual coloring it in the UI - symbols are for bash only. Maybe we

Re: [VOTE] Changes in import paths

Hi Jarek, No worries. I must admit that I've lost track a bit when the case 3+4 got combined. Maybe for the future better to let the current vote run and maybe reinitiate a new vote if there are new options. Currently, it is quite easy to think of a few obvious groups, but it is so hard to keep t

Re: [Discuss] AIP-23 Proposal "Migration out of Travis CI"

Some update on my GitLab experiences so far: TL;DR; I think the POC has shown that we can fairly easily replicate the CI in GitLab + Kubernetes. I think i can say - it generally works, I can plug it in for master/v1-10-test builds in the main Airflow project for a few weeks to see how it is doing

Re: [VOTE] Release Airflow 1.10.4 from RC5

+1 (non-binding) Works for me and k8s executor is not hanging with that version. Thanks Kamil - Kamil Gałuszka Principal Architect FLYR, Inc. www.flyrlabs.com On Sun, Aug 4, 2019 at 12:30 AM Kaxil Naik wrote: > +1 (binding) > > No installation issues. Fresh install works

Re: [VOTE] Changes in import paths

Hey Fokko, Really sorry, to miss this . I see now that you have not voted because you thought it will be transferred automatically -it was thought as not and additional option but combined replacement for (3+4) cases. This was after I realised that there was a veto for namespaces from Ash and I

Re: [VOTE] Changes in import paths

Hi Jarek, Just wondering how the vote is unanimous. On case 3 I've voted for B. I still believe introducing namespaces is hard to maintain, as I explained earlier: Mostly because it isn't as trivial to decide when it gets its own package or not. Besides the cloud providers, there are companies lik

Re: [VOTE] Changes in import paths

Seems that after this months of discussion we got an unanimous voting result. I summarised it in the AIP-21 and changed its status to "Accepted". Thanks for all your feedback! We will start soon moving GCP opera

Re: Upcoming Apache Airflow Meetup in NYC

Awesome! I've registered this meetup. Looking forward to attending the event! I am also interested in any session you will host. Thank you very much! On Mon, Aug 5, 2019 at 9:15 AM Jarek Potiuk wrote: > I will be speaking at NYC “Apache Airflow Meetup” on 26th of August with > “It’s a Breeze to

Upcoming Apache Airflow Meetup in NYC

I will be speaking at NYC “Apache Airflow Meetup” on 26th of August with “It’s a Breeze to develop Airflow” talk. It’s quite possible there will be a hands-on workshop for basics of Apache Airflow Development. https://www.meetup.com/NYC-Apache-Airflow-Meetup/events/263735215/ I will also be aroun

POST request of Experimental REST API

Hi All, Sorry, I can manage this problem. Thanks and Regards, Nimesha

POST request of Experimental REST API

Hi All, My POST request of Experimental REST APIs are not working. I hope a solution for this issue Thanks and Regards, Nimesha