[VOTE] Release Apache Airflow 1.10.5rc1 as 1.10.5

Hey all, I have cut Airflow 1.10.5 RC1. This email is calling a vote on the release, which will last for 72 hours. Consider this my (binding) +1. Airflow 1.10.5 RC1 is available at: https://dist.apache.org/repos/dist/dev/airflow/1.10.5rc1/ *apache-airflow-1.10.5rc1-source.tar.gz* is a source rel

[RESULT][VOTE] Apache Airflow 1.10.5rc1 as 1.10.5

Hello, Apache Airflow 1.10.5 (based on rc1) has been accepted. 3 “+1” binding votes received: - Kaxil Naik (binding) - Ash Berlin-Taylor (binding) - Fokko Driesprong (binding) No negative ("-1") votes received. Vote thread: https://lists.apache.org/t

Apache Airflow 1.10.5 is released

Dear Airflow community, I'm happy to announce that Airflow 1.10.5 was just released. The source release, as well as the binary "sdist" release, are available here: https://dist.apache.org/repos/dist/release/airflow/1.10.5/ (Older releases are available from https://archive.apache.org/dist/airflo

Re: [ANNOUNCE] Please welcome new Airflow committer Felix Uellendall

Congratulations Felix On Mon, Sep 9, 2019 at 2:03 PM Jarek Potiuk wrote: > Congrats Felix! > > pon., 9 wrz 2019, 12:58 użytkownik Ash Berlin-Taylor > napisał: > > > All, > > > > I'm pleased to announce that the Airflow PMC has voted in Felix > Uellendall > > to be > > a committer. Felix has bee

Re: [DISCUSS] Donating Airflow k8s Operator

+1 On Thu, Sep 12, 2019, 10:22 Ash Berlin-Taylor wrote: > +1 > > My only "concern" is what we call it - the term operator clashes between > Kubernetes and Airflow to mean different things. > > -ash > > On 12 September 2019 08:22:39 CEST, Tao Feng wrote: > >+1 as well. One question: does the ori

Re: [DISCUSS] Donating Airflow k8s Operator

Agree to Ash's comment. On Thu, Sep 12, 2019, 11:37 Andrii Soldatenko wrote: > +1 > +1 to Ash comment, maybe "airflow-k8s-operator" or something in this > manner. > > On Thu, Sep 12, 2019 at 12:25 PM Kaxil Naik wrote: > > > +1 > > > > O

Re: [PLEASE PARTICIPATE][AIP-11] UX phase of Airflow website

Good job guys. Really like the documentation page. My opinion is that it would be better to have Case Studies as Blog Posts instead of a separate page just like Google Cloud blog. This gives us room to have as many case studies as we want. jmeic...@quantopian.com - Version selector is already th

Re: AIP-7 completed :)

Awesome work Jarek :) On Wed, Sep 18, 2019 at 10:36 PM Jarek Potiuk wrote: > Hello Airflow developers, > > We just merged the last change related to Breeze - AIP-7 > Simplified Development Workflow > < > https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals?src=brea

Re: Setting to add choice of schedule at end or schedule at start of interval

Aug 23, 2019 at 8:24 AM Jarek Potiuk < > jarek.pot...@polidea.com> > >> > wrote: > >> > > >> > > Happy for it as well. There are a number of cases where scheduling > at > >> > start > >> > > makes more sense and as we see Airflow

Re: Setting to add choice of schedule at end or schedule at start of interval

t new users of Airflow, but > also will break a _lot_ of DAGs. I feel like if we don't change this in 2.0 > we probably won't for any 2.x either, which would be a shame. > > On Wed, Sep 25, 2019 at 8:33 PM Kaxil Naik wrote: > > > I agree with Dan to change the de

Merging PRs

Hello, all committers & PMC members, Whenever your merge PRs, please make sure that the commit message follows the following structure: *[AIRFLOW-XXX] COMMIT_MSG (#PR_NUMBER)* Example: *[AIRFLOW-5574] Fix Google Analytics script loading (#6218)* This will make our Changelog easy to read too :)

Re: [AIP-11] Airflow Brandbook

Awesome !! On Thu, Oct 3, 2019 at 11:37 AM Driesprong, Fokko wrote: > Awesome! Love it > > Cheers, Fokko > > Op do 3 okt. 2019 om 13:18 schreef Ash Berlin-Taylor > > > Great! > > > > Could someone upload that to the logo file list space on the wiki? > > > > (Or I can do it tomorrow when I'm bac

Re: AIP-21 - grouping google operators

I am fine with it. Looks more logical. On Thu, Oct 3, 2019, 17:01 Jarek Potiuk wrote: > As part of AIP-21 we are moving the operators to core. > > We have been discussing during the last few days how we should group the > operators from Google (we included Google Composer team) and we came to th

Re: [PROPOSAL] Migrate to Pytest

+1 for pytest On Mon, Oct 14, 2019 at 2:46 PM Bas Harenslak wrote: > Big +1 for pytest > > Bas > > > On 14 Oct 2019, at 15:29, Jarek Potiuk wrote: > > > > Fantastic! Pytest is sooo much better than nosetests! > > > > On Mon, Oct 14, 2019 at 1:44 PM Ash Berlin-Taylor > wrote: > > > >> Awesome,

[VOTE] AIP-24: Persisting serialized DAG in DB for webserver scalability

*Previous Mailing List discussion*: https://lists.apache.org/thread.html/65d282368e0a7c19815badb8b1c6c8d72b0975ce94f601e13af44f74@%3Cdev.airflow.apache.org%3E . *Authors*: Kaxil Naik, Zhou Fang, Ash-Berlin Taylor *Summary*: - DAGs are serialized using JSON format and stored in a SerializedDag

Re: [VOTE] AIP-24: Persisting serialized DAG in DB for webserver scalability

ld be nice to see more detailed notes about how > > >> this > > >>>> will play out in the future. We shouldn't walk into a system that > > >> causes > > >>>> more pain in the future. (I can't say for sure that it does, but I > > >>

New PMC Member: Jarek Potiuk

and involved in the discussion of other AIPs Being a PMC member enables assistance with the management and to guide the direction of the project. Congratulations Jarek, keep doing the great work !! Cheers, Kaxil Naik, on behalf of Airflow PMC

Re: Announcing SIG-Knative/ The Monthly Knative Executor Meetup/Call-for-contributers

Either we would record or have meeting notes :) On Fri, Oct 18, 2019 at 11:27 PM Kevin Yang wrote: > Sry that I didn't notice the event is 8am-9am. Can we the events recorded > by any chance? > > On Thu, Oct 17, 2019 at 11:10 PM Maxime Beauchemin < > maximebeauche...@gmail.com> wrote: > > > Nice

Re: [VOTE] Release 1.10.6 from 1.10.6rc1

+1 (binding) - tested on Py 3.7.3 with example DAGs On Sat, Oct 19, 2019 at 11:30 AM Ash Berlin-Taylor wrote: > I did all my testing of the RC on 3.7.3 so the bits I testee (core mostly, > didn't test many operators) work > > On 19 October 2019 07:56:40 BST, Jarek Potiuk > wrote: > >It is state

Re: [VOTE] AIP-24: Persisting serialized DAG in DB for webserver scalability

This vote passed (although not unanimous) and I'll mark this AIP as accepted. *Result*: +1 votes: 7 (6 binding and 1 non-binding vote) -1 votes: 2 (2 binding and 0 non-binding votes) *+1 (binding)*: Kaxil Naik Ash-Berlin Taylor Jarek Potiuk Kamil Breguła Fokko Driesprong Sumit Maheshwari

Re: [VOTE] AIP-24: Persisting serialized DAG in DB for webserver scalability

://github.com/apache/airflow/pull/5992) ready and that too is becoming nightmare to maintain. Regards, Kaxil On Wed, Oct 23, 2019, 23:39 Kaxil Naik wrote: > This vote passed (although not unanimous) and I'll mark this AIP as > accepted. > > *Result*: > +1 votes: 7 (6 bindi

Re: [VOTE] AIP-24: Persisting serialized DAG in DB for webserver scalability

>> approaches > > > >>> Ash mentioned or can even create another table and let them coexist > > > for a > > > >>> while if the change is dramastic. > > > >>> > > > >>> The added DB load seems pret

Re: [VOTE] Release 1.10.6 from 1.10.6rc2

+1 (binding) On Sat, Oct 26, 2019 at 12:05 AM Driesprong, Fokko wrote: > +1 binding from my side > > Ran an example DAGs with Docker using Python 3.7. > > We might need to check why AIRFLOW-5746 is being reverted: > https://github.com/apache/airflow/pull/6434 > > If there is another RC, I'd like

Re: [VOTE] Release 1.10.6 from 1.10.6rc2

est does not > really > > >> test what it should (passing PYTHONPATH to impersonated tasks) but the > > >> functionality (impersonation + path) has not actually changed and it > > works. > > >> The test worked fine before the change was added - it's just impor

Re: AIP-21 (Move operators to Core) - "cross_transfer" packages

Also, ansible has something similar: https://github.com/ansible/ansible/tree/devel/lib/ansible/modules Generally, I have been inspired by how Terraform and Ansible have implemented it and can serve as an inspiration to us. On Tue, Oct 29, 2019 at 12:51 PM Ash Berlin-Taylor wrote: > Also provide

Re: [PROPOSE] Ease future migration path to 2.0 by provider's operators/hook backporting to 1.10.*

The namespace feature looks promising and from your tests, it looks like it would work well from Airflow 2.0 and onwards. I will look at it in-depth and see if I have more suggestions or opinion on it On Tue, Oct 29, 2019 at 3:32 PM Jarek Potiuk wrote: > TL;DR; We did some testing about namespa

Re: Tomorrow is our first SIG-Knative meeting

Looking forward !! Thanks Daniel On Tue, Oct 29, 2019 at 9:40 PM Daniel Imberman wrote: > Hello fellow Airflowers! > > Wanted to send a quick reminder that our first airflow SIG-knative meeting > will take place tomorrow morning at 11AM EST! We'll be going to go over > the > proposed architectu

Re: [PROPOSAL] Migrate to Pytest

+1 pytest is way better On Wed, Oct 30, 2019 at 3:59 PM Driesprong, Fokko wrote: > +1 Can't wait! > > Op wo 30 okt. 2019 om 16:57 schreef Ash Berlin-Taylor : > > > I'm not sure this even warrants an AIP. What do people think? Once the > > tests are passing (and making them pass is a good thing a

Re: [PROPOSAL] Migrate to Pytest

And yes we should merge it as soon as we have all green On Wed, Oct 30, 2019 at 4:28 PM Kaxil Naik wrote: > +1 pytest is way better > > On Wed, Oct 30, 2019 at 3:59 PM Driesprong, Fokko > wrote: > >> +1 Can't wait! >> >> Op wo 30 okt. 2019 om 16:57 schre

Re: Inconsistent class names for AWS integrations

I think amazon/aws is better for 2 reasons: - Consistent with what we are doing with google - There can be API services for Amazon platform like https://developer.amazon.com/apps-and-games/incentives-api | https://developer.amazon.com/docs/app-submission-api/overview.html etc On Thu

Re: [PROPOSE] Ease future migration path to 2.0 by provider's operators/hook backporting to 1.10.*

some nicer/shorter one: "airflow_ext", "airflow_int", > "airflow_x", "airflow_mod", "airlfow_next", "airflow_xt", "airflow_", > "ext_airflow", Interestingly "airflow_" is the one suggested by P

Re: [PROPOSE] Ease future migration path to 2.0 by provider's operators/hook backporting to 1.10.*

package (+ separate release > > > schedule > > > for backporting needs) > > > Here again the structure of repo (we will likely be able to use native > > > namespaces so I removed some needles __init__.py). > > > > > > |-- airflow > > >

Re: [VOTE] AIP-21 update for Airflow 1.10.* backportability

I think we should keep the vote open at least until mid next week to have more thought and inputs on this one. In general, I am happy with the approach but operators/hooks and sensors shouldn't be a provider. "hadoop" can be its provider and hdfs can be a part of it. providers/ google

Re: [VOTE] AIP-21 update for Airflow 1.10.* backportability

rs-and-hooks-ref.html#software-operators-and-hooks > > On Fri, Nov 8, 2019 at 3:47 PM Kaxil Naik wrote: > > > > I think we should keep the vote open at least until mid next week to have > > more thought and inputs on this one. > > > > In general, I am happy w

Re: [VOTE] AIP-21 update for Airflow 1.10.* backportability

t; > > > > > http > > > > > > > > > > > > grpc > > > > > > > > > > > > smtp > > > > > > > > > > > > jdbc > > > > > > > > > > > > wi

Re: [VOTE] AIP-21 update for Airflow 1.10.* backportability

rom > core? These are the elements that are installed in every environment > because they are required by Airflow, so moving them to a separate > installed package is pointless in my opinion. > > On Mon, Nov 11, 2019 at 3:07 PM Kaxil Naik wrote: > > > > I am fine with th

Re: [VOTE] AIP-26 Production ready Airflow Docker image and helm chart

I haven't had a chance to look at the PR yet. But +1 (binding) for the AIP. On Tue, Nov 12, 2019 at 3:23 PM Jarek Potiuk wrote: > Hmm. Would love some votes :). Mine is +1 (binding) > > On Wed, Nov 6, 2019 at 10:52 PM Jarek Potiuk > wrote: > > > Hello Airflow community, > > > > Here is another

Re: Drop Python 3.5 support?

+1 On Tue, Nov 12, 2019 at 9:47 PM Dan Davydov wrote: > +1 > > On Tue, Nov 12, 2019 at 4:46 PM Jarek Potiuk > wrote: > > > Yep. It was actually a '+1' in disguise Bolke :). > > > > On Tue, Nov 12, 2019 at 10:44 PM Christian Lellmann > > wrote: > > > > > +1 from my side too! > > > > > > Bolke d

Re: [VOTE] 2nd attempt for AIP-21 update for Airflow 1.10.* backportability

I just have 1 comment: Should we have a "*airflow.core*" (or airflow.providers) for all the hooks/operators listed under *fundamentals *as I feel we are going to have "airflow.providers.gcp", "airflow.providers.amazon", "airflow.providers.apache"? What do you all think? Maybe it is not necessary

Re: [VOTE] 2nd attempt for AIP-21 update for Airflow 1.10.* backportability

ooks', 'airflow.sensors' for those. It feels > natural and having them 'higher' in the tree hierarchy is a good way to > show that they are fundamental part of Airflow. > > J > > pt., 15 lis 2019, 16:49 użytkownik Kaxil Naik > napisał: > > > I

Re: [VOTE] Accept new Airflow website contribution

Awesome job guys. Few small comments: - Can we please use Airflow logo with transparent background in *favicon* ? - Does the box have more padding than needed in the header? Screenshot below: [image: image.png] - Should we Remove the text in RoadMap and show TBD or something whe

Re: [VOTE] Accept new Airflow website contribution

Sent on Slack On Fri, Nov 15, 2019 at 10:45 PM Kamil Breguła wrote: > Hello, > > The mailing list does not support attachments. Can you forward a photo to > me? > > Best regards, > > On Fri, Nov 15, 2019 at 11:41 PM Kaxil Naik wrote: > > > > Awesome

Closing JIRA Issue for Merged PRs

Hi Committers, Please make sure to close the Jira issues if the related PRs are merged. I am going through the Jira Reports (Image: https://imgur.com/n50Ticx) and was concerned with the gap between issues created & resolved in recent months. However, I noticed while going through the jira issues

Re: Closing JIRA Issue for Merged PRs

ntion. > > On Fri, Nov 15, 2019 at 4:06 PM Kaxil Naik wrote: > > > Hi Committers, > > > > Please make sure to close the Jira issues if the related PRs are merged. > > > > I am going through the Jira Reports (Image: https://imgur.com/n50Ticx) > and > &g

Re: Closing JIRA Issue for Merged PRs

you guessed it) > > > >automate > > > >> it > > > >> > > :). Either with JIRA/Github integration or some automated tool > to > > > >do it > > > >> > > regularly and resolving all already mer

Re: Closing JIRA Issue for Merged PRs

s close them. But it's not ideal of course. > > > > >> > > > > > > >> > > However simple it is - I think we are just humans and we will > > > > >forget > > > > >> from > > > > >> > > time

Re: Closing JIRA Issue for Merged PRs

: > > >>>>>> > > >>>>>>> And yes. I was one of the culprits - I saw :(. Sorry about that > > >>>>> Kaxil. > > >>>>>>> Just hope we can streamline this :). > > >>>>>>> >

Re: [VOTE] Accept new Airflow website contribution

;ve done guys! > >> So from me it's +1 (non-binding). > >> > >> Bests, > >> Tomek > >> > >> On Sat, Nov 16, 2019 at 12:10 AM Kaxil Naik > wrote: > >> > >>> Sent on Slack > >>> > >>> On Fri, No

Re: [VOTE] Accept new Airflow website contribution

ttps://docs.google.com/document/d/1Y4jBjtQ13zeLZ2e3V4foa51pN-168p1DHJ5zc7cbyGg/edit# > > Regards, > Kamil > > On Wed, Nov 20, 2019 at 2:44 PM Kaxil Naik wrote: > > > > +1 (binding) as long as we fix the points I mentioned in the last email > :) > > > > On Wed, Nov 20,

Re: [VOTE] Accept new Airflow website contribution

I am not much worried about content. It can be a WIP and we can keep on improving. On Wed, Nov 20, 2019 at 3:22 PM Kaxil Naik wrote: > Check the navbars of other sites like https://spark.apache.org/ or even > https://cloud.google.com/ for that matter. > > The current navbar at htt

Re: [Discuss] Airflow Summits 2020

I think this needs to go for voting. My Proposal is just *Airflow Summit* 😁 On Wed, Nov 20, 2019 at 5:07 PM Soma S Dhavala wrote: > +1 airflow current > > On Wed, Nov 20, 2019 at 10:05 PM Jonathan Miles wrote: > > > +1 I like the double meaning of Airflow Current > > > > There are also things y

Re: Closing JIRA Issue for Merged PRs

gt;> > Just hope we can streamline this :). > > > > > > >> > > > > > > > >> > On Sat, Nov 16, 2019 at 10:12 AM Jarek Potiuk > > > > > > > > > > > > > >> > wrote: > > > > > > >&g

Re: [VOTE] Accept new Airflow website contribution

[image: Github] <https://github.com/Polidea> [image: Facebook] > > <https://www.facebook.com/Polidea.Software> [image: Twitter] > > <https://twitter.com/polidea> [image: Linkedin] > > <https://www.linkedin.com/company/polidea> [image: Instagram] > > &l

Re: [VOTE] Accept donation of Airflow k8s Operator to Apache Airflow

+1 (binding) On Thu, Nov 21, 2019, 01:04 Aizhamal Nurmamat kyzy wrote: > Hi everyone, > > We have previously discussed the donation of Airflow k8s operator [1], that > was originally developed by Barni (cc'ed) [2] and who has agreed to donate > it to Apache Airflow. > > Barni has been working wi

Re: [DISCUSS] Airflow Summits dates and locations

+1 for the proposed dates and location. On Thu, Nov 21, 2019 at 4:46 AM Maxime Beauchemin < maximebeauche...@gmail.com> wrote: > +1, the proposed dates and location seems reasonable to me. > > My heart would pick Paris but London is more rational :) > > Max > > On Wed, Nov 20, 2019 at 3:46 PM Aiz

Re: [VOTE] Accept donation of Airflow k8s Operator to Apache Airflow

om/k/d/mailapp?ct=dx&cv=10.0.32&pv=10.14.5&source=email_footer_2 > ] > On Thu, Nov 21, 2019 at 9:39 AM, Jarek Potiuk > wrote: > +1 (binding) > > On Thu, Nov 21, 2019 at 9:27 AM Kaxil Naik wrote: > > > +1 (binding) > > > > On Thu, Nov 21, 2019, 01:0

Re: New PMC members: Aizhamal and Kevin

Congratulations Aizhamal & Kevin. Well deserved. Keep up the good work. Regards, Kaxil On Fri, Nov 22, 2019, 10:36 Tomasz Urbaszek wrote: > Congratulations Aizhamal i Kevin! > > Bests, > Tomek > > On Fri, Nov 22, 2019 at 11:30 AM Ash Berlin-Taylor wrote: > > > The PMC (Project Management Comm

Re: [PROPOSAL] Migrate to Pytest

; > appreciated! > > > ;) > > > https://github.com/apache/airflow/pull/6472 > > > > > > Travis's red due to one test (test_on_kill) but it can be fixed as seen > > in > > > previous commits. > > > > > > Bests, > > > Tome

Re: Closing JIRA Issue for Merged PRs

add some > useful integrations already ? > > J. > > > On Wed, Nov 20, 2019 at 8:22 PM Kaxil Naik wrote: > > > I just used it on my fork and works nicely. Thanks, Max. > > > > +1 for probot > > > > On Tue, Nov 19, 2019 at 10:55 PM Jarek Potiuk >

Re: Apache Airflow welcomes Kengo Seki (sekikn) as committer & PMC member

Congratulations Kengo 🎉 On Sun, Dec 1, 2019, 08:32 Jarek Potiuk wrote: > Congrats Kengo! Looking forward to work with you :). > > J. > > On Sun, Dec 1, 2019 at 3:05 AM Sid Anand wrote: > > > Hi Folks! > > The PMC (Project Management Committee) would like to welcome aboard Kengo > > Seki (sekikn

Re: [DISCUSS] Using asserts in airflow code

Wouldn't it just make sense to remove asserts and use IF condition so that we don't need to set any rules when to assert and when to not assert. I don't see a huge benefit of using assert but I can see how it can be mis-used (used when it shouldn't not be used) sometimes. Regards, Kaxil On Wed,

Re: [VOTE] Allow using asserts in Airflow code

-1 (binding) it definitely seems to be a source of confusion and comparing it to the advantages it provides, I would be hesitant on using it. On Thu, Dec 5, 2019 at 2:56 PM Jarek Potiuk wrote: > Here is a quick vote on using asserts in Airflow code. > > It is distilled from the discussion > http

Re: [DISCUSS] Approach for JIRA AIRFLOW-5523

Did you reproduce this issue with the current Airflow Master? I think the issues was solved in master On Fri, Dec 6, 2019, 09:37 Vishesh Jain wrote: > Hi Team > > I am working on JIRA AIRFLOW-5523 > . > > As per the JIRA, the requirement is to

Re: [DISCUSS] Revenge of the asserts

Yup, we should. On Mon, Dec 9, 2019 at 3:20 PM Ash Berlin-Taylor wrote: > Absolutely, and I don't think any of the concers about it in run-time code > apply! Plus it is the way pytest recommends, and I think we get nicer > failure messages using assert-style too? > > -a > > On 9 December 2019 15

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

+1 for Github actions On Mon, Dec 9, 2019, 22:16 Ash Berlin-Taylor wrote: > Happy with any thing that gives a more seamless CI experience - faster is > good too! > > -a > > On 9 December 2019 22:12:05 GMT, Aizhamal Nurmamat kyzy < > aizha...@apache.org> wrote: > >+1 on GitHub Actions. > > > >On

Re: [DISCUSS] Approach for JIRA AIRFLOW-5523

n dag file doesn't exist: >In this case, dag is deleted forever along with history. > > > > Thanks > Vishesh Jain > > > On Fri, Dec 6, 2019 at 3:15 PM Kaxil Naik wrote: > > > Did you reproduce this issue with the current Airflow Master? I think t

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

ithub.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets > > > > > > needs someone with Admin rights to create, and I don't see the Settings > > tab > > > at all. > > > > > > -as

Re: Test fixtures for repeatable (performance) tests?

https://github.com/FactoryBoy/factory_boy looks good for creating Fixtures. Good example and article about it here: https://medium.com/@vittorio.camisa/agile-database-integration-tests-with-python-sqlalchemy-and-factory-boy-6824e8fe33a1 PS: I have tried or tested it yet On Fri, Dec 13, 2019 at 3

Re: Setting fixVersion and "Resolved" status in JIRA

I think until we find the solution all of us (PMC + Committers) need to own it up and *Resolve* the Jira issues when we merge the PRs. Previously we use the CLI that Bolke created to Close/Merge the PR which would also automatically Resolve the Jira issue with the correct version. Check this: http

Re: Setting fixVersion and "Resolved" status in JIRA

= "Apache Airflow" AND fixVersion is EMPTY AND issue in > () > > To find all "missed" issues. > > J. > > On Tue, Dec 17, 2019 at 11:00 PM Kaxil Naik wrote: > > > I think until we find the solution all of us (PMC + Committers) need to > own >

Re: [DISCUSS] Revenge of the asserts

M Jarek Potiuk < > jarek.pot...@polidea.com> > > > > wrote: > > > > > > > > > Well. I think (as discussed with Kamil) maybe even convert the > tests > > > > > automatically. > > > > > > > > > &

[VOTE] Release 1.10.7 from 1.10.7rc1

Hey all, I have cut Airflow 1.10.7 RC1. This email is calling a vote on the release, which will last for 96 hours, until Monday, December 23nd at 12:20 UTC. (I've extended the vote by one day to give two working days to test.) Consider this my (binding) +1. Airflow 1.10.7 RC1 is available at: <

Re: [VOTE] Release 1.10.7 from 1.10.7rc1

Canceling this vote as we found a bug with Flask for Py2. On Thu, Dec 19, 2019 at 12:18 PM Kaxil Naik wrote: > Hey all, > > I have cut Airflow 1.10.7 RC1. This email is calling a vote on the > release, which will last for 96 hours, until Monday, December 23nd at 12:20 > UTC. (I&

[VOTE] Release 1.10.7 from 1.10.7rc2

Hey all, I have cut Airflow 1.10.7 RC2. This email is calling a vote on the release, which will last for 96 hours, until Monday, December 23nd at 22:00 UTC. (I've extended the vote by a day to give two working days to test.) Consider this my (binding) +1. Airflow 1.10.7 RC2 is available at: < ht

Re: Quick note - JS/front end deps are now managed by Yarn, no longer NPM

🎉 On Thu, Dec 19, 2019 at 10:07 PM Ash Berlin-Taylor wrote: > Hi everyone, > > Just a quick note that as of master a few minutes ago front end deps are > now managed by https://yarnpkg.com/ , not npm. I > finally got fed up of bugs in npm where the suggested fix was to dele

[VOTE] Add Probot Integrations to Airflow Github Repo

Hello all, I would like to propose that we add the following ProBot integrations to Airflow repo: - https://github.com/apps/ci-reporter - Works with your project's CI tool to report failed builds into the relevant PR. - https://github.com/apps/mergeable - Prevents merging of Pull Request

Re: [VOTE] Release 1.10.7 from 1.10.7rc2

Canceling this vote too as we found a bug with Marshmallow (dependency of Flask-appbuilder). On Thu, Dec 19, 2019 at 10:03 PM Kaxil Naik wrote: > Hey all, > > I have cut Airflow 1.10.7 RC2. This email is calling a vote on the > release, which will last for 96 hours, until Monday, D

[VOTE] Release 1.10.7 from 1.10.7rc3

Hey all, I have cut Airflow 1.10.7 RC3. This email is calling a vote on the release, which will last for 96 hours, until Tuesday, December 24nd at 12:30 UTC. (I've extended the vote by a day to give two working days to test.) Consider this my (binding) +1. Airflow 1.10.7 RC3 is available at: < h

Re: New Committer: Tomasz Urbaszek

Congrats Tomasz, welcome aboard and well deserved. On Fri, Dec 20, 2019, 15:28 Jarek Potiuk wrote: > Congrats Tomek! Great job! Well deserved indeed! > > J. > > On Fri, Dec 20, 2019 at 4:14 PM Felix Uellendall > wrote: > > > Congrats Tomek! Well deserved :) ! > > > > Sent from ProtonMail Mobile

Airflow Summit Survey

Hi all, We are planning to organize 2 Airflow summits in 2020, one in North America, one in Europe. These summits will be community events, and an opportunity to bring together users and contributors of Apache Airflow, and collaborate on the development of the project. We would like to tailor th

Re: [VOTE] Release 1.10.7 from 1.10.7rc3

blem). That said, maybe that output > _should_ go through a logger. > > -ash > > > On 20 Dec 2019, at 12:36, Kaxil Naik wrote: > > > > Hey all, > > > > I have cut Airflow 1.10.7 RC3. This email is calling a vote on the > release, > > which will last for

[RESULT][VOTE] Release 1.10.7 from 1.10.7rc3

Hello, Apache Airflow 1.10.7 (based on rc3) has been accepted. 3 “+1” binding votes received: - Kaxil Naik (binding) - Jarek Potiuk (binding) - Ash Berlin-Taylor (binding) No negative ("-1") votes received. Vote thread: https://lists.apache.org/t

Apache Airflow 1.10.7 released!

Dear Airflow community, I'm happy to announce that Airflow 1.10.7 was just released. The source release, as well as the binary "sdist" and wheel bundles, are available here: https://dist.apache.org/repos/dist/release/airflow/1.10.7/ We also made this version available on PyPi for convenience (p

Re: [PROPOSAL] [FUTURE] Semi-automated tool for migration to 2.0.0

Yes definitely, I had thought of something like py2to3 script. We might want to create something similar. On Sun, Dec 29, 2019, 14:17 Jarek Potiuk wrote: > Great Claudio! Once we get closer to starting it, we can start some joined > work on it :). > > I think we also will need the support of a

Re: [VOTE] Add Probot Integrations to Airflow Github Repo

Thanks Max, I will raise a JIRA with the INFRA to add that too. Btw I had raised a request for the 4 integrations https://issues.apache.org/jira/browse/INFRA-19607 but looks like it hasn't gained any traction from them yet. On Fri, Dec 20, 2019 at 8:29 PM Maxime Beauchemin < maximebeauche...@g

Re: [NON-TECHNICAL] [DISCUSS] Being even more welcoming community ?

We also have Airflow Slack : https://apache-airflow-slack.herokuapp.com/ The reason why we also having mailing list is slack messages are not indexed by Google or other search engines. On Mon, Dec 30, 2019 at 2:11 PM Anton Zayniev wrote: > I'm fairly new to Airflow community and I'd like to s

Re: [VOTE] Add Probot Integrations to Airflow Github Repo

r. I > guess > > Xmas period got in the way. > > > > J. > > > > On Mon, Dec 30, 2019 at 5:15 AM Kevin Yang wrote: > > > >> +1! > >> > >> Kaxil Naik 于2019年12月29日 周日下午6:21写道： > >> > >> > Thanks Max, > >

Re: [VOTE] Add Probot Integrations to Airflow Github Repo

uk > > wrote: > > > > > Seems like we have a new friendly bot :) > > > > > > On Mon, Dec 30, 2019 at 8:41 AM Jarek Potiuk > > > > wrote: > > > > > > > I opened a few tickets for INFRA and I am also waitin

Re: [VOTE] Add Probot Integrations to Airflow Github Repo

much > better than commitlint looking at your recent configuration :) > > On Tue, Dec 31, 2019 at 2:14 PM Kaxil Naik wrote: > > > Once we have got all the configs for the current integrations, I will > > review the ones you have provided in the link above and see if it is >

Re: Test style convention after migration to pytest

This is a tough one. Both arguments are reasonable. I agree at some point we should convert all to use assert. But at the same time, we should also focus on adding *more user-facing features *and spend less time on more refactor or similar changes. So based on that, this might be a low priority.

[DISCUSS] Airflow Website Blog Guidelines

Hey all, I wanted to raise a point regarding our Blog on the Airflow website. There is an open PR: https://github.com/apache/airflow-site/pull/231 from Chandu Kavar to add 2 blog posts based on his nicely written Airflow testing material. However, the blog post basically links back to the origin

Re: [VOTE] Add Probot Integrations to Airflow Github Repo

Yeah the mention-bot was archived and is no longer maintained. On Fri, Jan 3, 2020 at 2:33 PM Tomasz Urbaszek wrote: > Hi all, > > I just discovered that some time ago we already used "mention-bot" that > suggests > potential reviewers based on history of changed files: > https://github.com/apac

Re: [VOTE] Add Probot Integrations to Airflow Github Repo

time contributors to integrate this in Airflow too. I have tested them on my other repo and works like a charm. Regards, Kaxil On Fri, Jan 3, 2020 at 2:38 PM Kaxil Naik wrote: > Yeah the mention-bot was archived and is no longer maintained. > > On Fri, Jan 3, 2020 at 2:33 PM T

Re: [DISCUSS] Airflow Website Blog Guidelines

tributors that we prefer original content. > > > > > > J > > > > > > On Fri, Jan 3, 2020 at 4:13 PM Jarek Potiuk > > > wrote: > > > > > > > +1. > > > > > > > > On Fri, Jan 3, 2020 at 3:43 PM Tomasz Urbaszek > > &g

Re: [VOTE] Add Probot Integrations to Airflow Github Repo

team will enable this soon as we just read permission and write-on labels. Regards, Kaxil On Fri, Jan 3, 2020 at 11:07 PM Kaxil Naik wrote: > I tried some Github actions today and fell in love. We don't even need to > ask for approval from INFRA team. > > I have raised 2 PRs: >

Re: [VOTE] Add Probot Integrations to Airflow Github Repo

until it is resolved in the original repo. Regards, Kaxil On Sat, Jan 4, 2020 at 1:07 AM Kaxil Naik wrote: > I think I was wrong. We still need permission from INFRA to enable the > GITHUB_TOKEN, I have raised an ISSUE with INFRA team: > https://issues.apache.org/jira/browse/I

Re: Killing Webserver/Scheduler gracefully

Systemd integrations have worked nicely for me: https://airflow.apache.org/docs/stable/howto/run-with-systemd.html On Sat, Jan 4, 2020 at 11:01 AM Jarek Potiuk wrote: > I would like to bring the subject from user@ group > > https://lists.apache.org/thread.html/5add5e8a19cb86ef2141d9d0634bd01c1

Re: Killing Webserver/Scheduler gracefully

executor POC and it's > helpful. > > T. > > On Sat, Jan 4, 2020 at 12:22 PM Kaxil Naik wrote: > > > Systemd integrations have worked nicely for me: > > https://airflow.apache.org/docs/stable/howto/run-with-systemd.html > > > > > > > > On

Re: [VOTE] Add Probot Integrations to Airflow Github Repo

out triaging/handling > PRs. > > J. > > > On Sat, Jan 4, 2020 at 3:28 AM Kaxil Naik wrote: > > > On digging further I found out that it is an open BUG on both the Github > > actions: > > > > Bug: https://github.com/actions/labeler/issues/12 or

Autolink References enabled for Airflow

Hi all, A couple of days back I opened an Issue with Apache Infra to autolink Jira references in commits: https://issues.apache.org/jira/browse/INFRA-19655 This is based on https://help.github.com/en/github/writing-on-github/autolinked-references-and-urls and works nicely, check the commit to se

  1   2   3   4   5   6   7   8   9   10   >