Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 14B47200C39 for ; Thu, 16 Mar 2017 16:53:57 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 11B51160B7A; Thu, 16 Mar 2017 15:53:57 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0BD00160B78 for ; Thu, 16 Mar 2017 16:53:55 +0100 (CET) Received: (qmail 67960 invoked by uid 500); 16 Mar 2017 15:53:53 -0000 Mailing-List: contact dev-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list dev@airflow.incubator.apache.org Received: (qmail 67948 invoked by uid 99); 16 Mar 2017 15:53:53 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Mar 2017 15:53:53 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id B0F811809F9 for ; Thu, 16 Mar 2017 15:53:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KAM_ASCII_DIVIDERS=0.8, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id g4KR9GLf5dCD for ; Thu, 16 Mar 2017 15:53:49 +0000 (UTC) Received: from mail-pg0-f46.google.com (mail-pg0-f46.google.com [74.125.83.46]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 6196D5F473 for ; Thu, 16 Mar 2017 15:53:48 +0000 (UTC) Received: by mail-pg0-f46.google.com with SMTP id b129so27085204pgc.2 for ; Thu, 16 Mar 2017 08:53:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=UXxkhE3s7HMsl/tDpekabMW1FzzTxlJj4w8qtnMRHhY=; b=UemXe6+BYE+qPxEG2xYQANdZy2loKr4Uw56lKuoizD0/1GJqy2/99aKYCmX/mmJnyE fLGgUsXDDp0lEt/5eKrCAFU2ectRRNNK4u2KtnGUiEV/6N92vwdhqnGQcIZjqIN4yX3L tHLwUgio2bC3cedcph7e/gbtxLzBkj8u7Q5ObPEGh92GFfjCaEH1RsPoRGlBQGPXqYPA FypEi3OlEmZtydQporsfFi/qTZ/dhDqyrLPZW495X4bWUS8ejScY0eWScvWE+qt8wvPy czYrKpn1ZieX6B33sqapQuju+p/U04/XAaboBJcLE+u93/zob/2IBvHMN+HmpFQWIKcd GoWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=UXxkhE3s7HMsl/tDpekabMW1FzzTxlJj4w8qtnMRHhY=; b=lviuqvLe29/8MikYdZ0lWQ5y8OC7/xTvnlfj3SGqhAaGrFDgBCfo9AWIeXz+lEwaxa efHB+9dn9gddSpJIIbEXx4IbXmsVWrqHvO2Dg8nYeSccIQAw1t9UjFNb0o/uvcr2EeDk e5L/2hNMuuR1P8BGcYkWpV5rmlBW0+qgSTnzjhkFGxwh+XcecEjH3X7dsmLpNwqqvBif tx91tTzPwwuYMcJllXH3thdItDcSnGv0envqEt1v4SuTIQ3Mvw2tSUih03kS9ngiyQ8Q IubN4W+e83UZNlS16X2l0ROl4DkRGPqmgoSNz/v6a1w7fdS6tgPoI4yo28IvGpqdb1Bk 8CNA== X-Gm-Message-State: AFeK/H14X6bwd3+lurEewvXElc1+U8hyeJFRyZZ67U3/RUgFm+U+JdJrdS8sxgA/n50TgA== X-Received: by 10.99.5.133 with SMTP id 127mr3219718pgf.8.1489679626408; Thu, 16 Mar 2017 08:53:46 -0700 (PDT) Received: from [192.168.218.15] ([156.39.191.26]) by smtp.gmail.com with ESMTPSA id 198sm11486605pgb.51.2017.03.16.08.53.44 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Mar 2017 08:53:45 -0700 (PDT) From: Bolke de Bruin Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: [VOTE] Release Airflow 1.8.0 based on Airflow 1.8.0rc5 Date: Thu, 16 Mar 2017 08:53:42 -0700 References: <3D35429E-4688-4A9F-B531-75BCB6DC2433@gmail.com> <997BD649-6668-4A8D-8A77-B93D7CF98214@gmail.com> <11BC4C56-8BAE-44BA-9D76-9E021789ECF9@gmail.com> To: dev@airflow.incubator.apache.org In-Reply-To: Message-Id: <76153308-82AA-4F1F-AECC-2248BB523641@gmail.com> X-Mailer: Apple Mail (2.3259) archived-at: Thu, 16 Mar 2017 15:53:57 -0000 I agree that it is not nice. I suggest that we revisit our fix and see = if we can do better there (rather than adding new complexity). And get = this into 1.8.1. Nevertheless, I consider the vote passed. Bolke > On 15 Mar 2017, at 19:12, Dan Davydov = wrote: >=20 > The only thing is that this is a change in semantics and changing = semantics > (breaking some DAGs) and then changing them back (and breaking things > again) isn't great. >=20 > On Wed, Mar 15, 2017 at 7:02 PM, Bolke de Bruin = wrote: >=20 >> Indeed that could be the case. Let's get 1.8.0 out the door so we can >> focus on these bug fixes for 1.8.1. >>=20 >> Bolke >>=20 >> Sent from my iPhone >>=20 >>> On 15 Mar 2017, at 18:25, Dan Davydov = >> wrote: >>>=20 >>> Another issue we are seeing is >>> https://issues.apache.org/jira/browse/AIRFLOW-992 - tasks that have = both >>> skipped children and successful children are run instead of skipped. = Not >>> blocking the release on this just letting you guys know for the = release >> bug >>> notes. We will be cherrypicking a fix for this onto our production = when >> we >>> release 1.8 once we come up with one. >>>=20 >>> It's possibly thought not necessarily related to an = incomplete/incorrect >>> fix of https://issues.apache.org/jira/browse/AIRFLOW-719 . >>>=20 >>>> On Wed, Mar 15, 2017 at 4:53 PM, siddharth anand = >> wrote: >>>>=20 >>>> Confirmed that Bolke's PR above fixes the issue. >>>>=20 >>>> Also, I agree this is not a blocker for the current airflow = release, so >> my >>>> +1 (binding) stands. >>>> -s >>>>=20 >>>>> On Wed, Mar 15, 2017 at 3:11 PM, Bolke de Bruin = >> wrote: >>>>>=20 >>>>> PR is available: = https://github.com/apache/incubator-airflow/pull/2154 >>>>>=20 >>>>> But marked for 1.8.1. >>>>>=20 >>>>> - Bolke >>>>>=20 >>>>>> On 15 Mar 2017, at 14:37, Bolke de Bruin = wrote: >>>>>>=20 >>>>>> On second thought I do consider it a bug and can have a fix out = pretty >>>>> quickly, but I don=E2=80=99t consider it a blocker. >>>>>>=20 >>>>>> - B. >>>>>>=20 >>>>>>> On 15 Mar 2017, at 14:21, Bolke de Bruin = wrote: >>>>>>>=20 >>>>>>> Just to be clear: Also in 1.7.1 the DagRun was marked = successful, but >>>>> its tasks continued to be scheduled. So one could also consider = 1.7.1 >>>>> behaviour a bug. I am not sure here, but I think it kind of makes = sense >>>> to >>>>> consider the behaviour of 1.7.1 a bug. It has been present = throughout >> all >>>>> the 1.8 rc/beta/apha series. >>>>>>>=20 >>>>>>> So yes it is a change in behaviour whether it is a regression or = an >>>>> integrity improvement is up for discussion. Either way I don=E2=80=99= t consider >>>> it >>>>> a blocker. >>>>>>>=20 >>>>>>> Bolke. >>>>>>>=20 >>>>>>>> On 15 Mar 2017, at 14:06, siddharth anand >> wrote: >>>>>>>>=20 >>>>>>>> Here's the JIRA : >>>>>>>> https://issues.apache.org/jira/browse/AIRFLOW-989 >>>>>>>>=20 >>>>>>>> I confirmed it is a regression from 1.7.1.3, which I installed = via >>>> pip >>>>> and >>>>>>>> tested against the same DAG in the JIRA. >>>>>>>>=20 >>>>>>>> The issue occurs if a leaf / last / terminal downstream task is = not >>>>>>>> cleared. You won't see this issue if you clear the entire DAG = Run or >>>>> clear >>>>>>>> a task and all of its downstream tasks. If you truly want to = only >>>>> clear and >>>>>>>> rerun a task, but not its downstream tasks, you can use the CLI = to >>>>> execute >>>>>>>> a specific task (e.g. vial airflow run). >>>>>>>>=20 >>>>>>>> This is a change in behavior -- if we do go ahead with the = release, >>>>> then >>>>>>>> this JIRA should be in a list of JIRAs of known issues related = to >> the >>>>> new >>>>>>>> version. >>>>>>>> -s >>>>>>>>=20 >>>>>>>> On Wed, Mar 15, 2017 at 9:17 AM, Chris Riccomini < >>>>> criccomini@apache.org> >>>>>>>> wrote: >>>>>>>>=20 >>>>>>>>> @Sid, does this happen if you clear downstream as well? >>>>>>>>>=20 >>>>>>>>> On Wed, Mar 15, 2017 at 9:04 AM, Chris Riccomini < >>>>> criccomini@apache.org> >>>>>>>>> wrote: >>>>>>>>>=20 >>>>>>>>>> Has anyone been able to reproduce Sid's issue? >>>>>>>>>>=20 >>>>>>>>>> On Tue, Mar 14, 2017 at 11:17 PM, Bolke de Bruin < >>>> bdbruin@gmail.com> >>>>>>>>>> wrote: >>>>>>>>>>=20 >>>>>>>>>>> That is not an airflow error, but a Kerberos error. Try = executing >>>>> the >>>>>>>>>>> kinit command on the command line by yourself. >>>>>>>>>>>=20 >>>>>>>>>>> Bolke >>>>>>>>>>>=20 >>>>>>>>>>> Sent from my iPhone >>>>>>>>>>>=20 >>>>>>>>>>>> On 14 Mar 2017, at 23:11, Ruslan Dautkhanov < >>>> dautkhanov@gmail.com> >>>>>>>>>>> wrote: >>>>>>>>>>>>=20 >>>>>>>>>>>> `airflow kerberos` is broken in 1.8-rc5 >>>>>>>>>>>> https://issues.apache.org/jira/browse/AIRFLOW-987 >>>>>>>>>>>> Hopefully fix can be part of the 1.8 release. >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> -- >>>>>>>>>>>> Ruslan Dautkhanov >>>>>>>>>>>>=20 >>>>>>>>>>>>> On Tue, Mar 14, 2017 at 6:19 PM, siddharth anand < >>>>> sanand@apache.org> >>>>>>>>>>> wrote: >>>>>>>>>>>>>=20 >>>>>>>>>>>>> FYI, >>>>>>>>>>>>> I've just hit a major bug in the release candidate related = to >>>>> "clear >>>>>>>>>>> task" >>>>>>>>>>>>> behavior. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> I've been running airflow in both stage and prod since >> yesterday >>>>> on >>>>>>>>>>> rc5 and >>>>>>>>>>>>> have reproduced this in both environments. I will file a = JIRA >>>> for >>>>>>>>> this >>>>>>>>>>>>> tonight, but wanted to send a note over email as well. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> In my example, I have a 2 task DAG. For a given DAG run = that >> has >>>>>>>>>>> completed >>>>>>>>>>>>> successfully, if I >>>>>>>>>>>>> 1) clear task2 (leaf task in this case), the >>>> previously-successful >>>>>>>>> DAG >>>>>>>>>>> Run >>>>>>>>>>>>> goes back to Running, requeues, and executes the task >>>>> successfully. >>>>>>>>>>> The DAG >>>>>>>>>>>>> Run the returns from Running to Success. >>>>>>>>>>>>> 2) clear task1 (root task in this case), the >>>> previously-successful >>>>>>>>> DAG >>>>>>>>>>> Run >>>>>>>>>>>>> goes back to Running, DOES NOT requeue or execute the task = at >>>> all. >>>>>>>>> The >>>>>>>>>>> DAG >>>>>>>>>>>>> Run the returns from Running to Success though it never = ran the >>>>> task. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> 1) is expected and previous behavior. 2) is a regression. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> The only workaround is to use the CLI to run the task = cleared. >>>>> Here >>>>>>>>> are >>>>>>>>>>>>> some images : >>>>>>>>>>>>> *After Clearing the Tasks* >>>>>>>>>>>>> https://www.dropbox.com/s/wmuxt0krwx6wurr/Screenshot% >>>>>>>>>>>>> 202017-03-14%2014.09.34.png?dl=3D0 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> *After DAG Runs return to Success* >>>>>>>>>>>>> https://www.dropbox.com/s/qop933rzgdzchpd/Screenshot% >>>>>>>>>>>>> 202017-03-14%2014.09.49.png?dl=3D0 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> This is a major regression because it will force everyone = to >> use >>>>> the >>>>>>>>>>> CLI >>>>>>>>>>>>> for things that they would normally use the UI for. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> -s >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> -s >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>>> On Tue, Mar 14, 2017 at 1:32 PM, Daniel Huang < >>>> dxhuang@gmail.com >>>>>>=20 >>>>>>>>>>> wrote: >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> +1 (non-binding)! >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> On Tue, Mar 14, 2017 at 11:35 AM, siddharth anand < >>>>>>>>> sanand@apache.org> >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> +1 (binding) >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> On Tue, Mar 14, 2017 at 8:42 AM, Maxime Beauchemin < >>>>>>>>>>>>>>> maximebeauchemin@gmail.com> wrote: >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> +1 (binding) >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> On Tue, Mar 14, 2017 at 3:59 AM, Alex Van Boxel < >>>>> alex@vanboxel.be >>>>>>>>>>=20 >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> +1 (binding) >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> Note: we had to revert all our ONE_SUCCESS with = ALL_SUCCESS >>>>>>>>> trigger >>>>>>>>>>>>>>> rules >>>>>>>>>>>>>>>>> where the parent nodes where joining with a SKIP. But = I can >>>> of >>>>>>>>>>>>> should >>>>>>>>>>>>>>>> have >>>>>>>>>>>>>>>>> known this was coming. Apart of that I had a = successful run >>>>> last >>>>>>>>>>>>>> night. >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> On Tue, Mar 14, 2017 at 1:37 AM siddharth anand < >>>>>>>>> sanand@apache.org >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> I'm going to deploy this to staging now. Fab work = Bolke! >>>>>>>>>>>>>>>>> -s >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> On Mon, Mar 13, 2017 at 2:16 PM, Dan Davydov < >>>>>>>>>>>>> dan.davydov@airbnb.com >>>>>>>>>>>>>> . >>>>>>>>>>>>>>>>> invalid >>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>> I'll test this on staging as soon as I get a chance = (the >>>>> testing >>>>>>>>>>>>> is >>>>>>>>>>>>>>>>>> non-blocking on the rc5). Bolke very much in = particular >> :). >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>> On Mon, Mar 13, 2017 at 10:46 AM, Jeremiah Lowin < >>>>>>>>>>>>>> jlowin@apache.org> >>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>> +1 (binding) extremely impressed by the work and >> diligence >>>>> all >>>>>>>>>>>>>>>>>> contributors >>>>>>>>>>>>>>>>>>> have put in to getting these blockers fixed, Bolke = in >>>>>>>>>>>>> particular. >>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>> On Mon, Mar 13, 2017 at 1:07 AM Arthur Wiedmer < >>>>>>>>>>>>>> arthur@apache.org> >>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>> +1 (binding) >>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>> Thanks again for steering us through Bolke. >>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>>> Arthur >>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>> On Sun, Mar 12, 2017 at 9:59 PM, Bolke de Bruin < >>>>>>>>>>>>>>> bdbruin@gmail.com >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>>> Dear All, >>>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>>> Finally, I have been able to make the FIFTH = RELEASE >>>>>>>>>>>>> CANDIDATE >>>>>>>>>>>>>>> of >>>>>>>>>>>>>>>>>>> Airflow >>>>>>>>>>>>>>>>>>>>> 1.8.0 available at: https://dist.apache.org/repos/ >>>>>>>>>>>>>>>>>>>>> dist/dev/incubator/airflow/ = >>>>>>>>>>>>>>>>>>>> repos/dist/dev/incubator/airflow/> , public keys = are >>>>>>>>>>>>>> available >>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>> = https://dist.apache.org/repos/dist/release/incubator/ >>>>>>>>>>>>>> airflow/ >>>>>>>>>>>>>>> < >>>>>>>>>>>>>>>>>>>>> = https://dist.apache.org/repos/dist/release/incubator/ >>>>>>>>>>>>>> airflow/> >>>>>>>>>>>>>>> . >>>>>>>>>>>>>>>>> It >>>>>>>>>>>>>>>>>> is >>>>>>>>>>>>>>>>>>>>> tagged with a local version = =E2=80=9Capache.incubating=E2=80=9D so it >>>>>>>>>>>>> allows >>>>>>>>>>>>>>>>>> upgrading >>>>>>>>>>>>>>>>>>>> from >>>>>>>>>>>>>>>>>>>>> earlier releases. >>>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>>> Issues fixed since rc4: >>>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-900] Double trigger should not kill = original >>>> task >>>>>>>>>>>>>>>> instance >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-900] Fixes bugs in LocalTaskJob for = double run >>>>>>>>>>>>>>>> protection >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-932] Do not mark tasks removed when >> backfilling >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-961] run onkill when SIGTERMed >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-910] Use parallel task execution for = backfills >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-967] Wrap strings in native for py2 ldap >>>>>>>>>>>>>> compatibility >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-941] Use defined parameters for psycopg2 >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-719] Prevent DAGs from ending prematurely >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-938] Use test for True in task_stats = queries >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-937] Improve performance of task_stats >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-933] use ast.literal_eval rather eval = because >>>>>>>>>>>>>>>>>> ast.literal_eval >>>>>>>>>>>>>>>>>>>>> does not execute input. >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-919] Running tasks with no start date >> shouldn't >>>>>>>>>>>>>> break >>>>>>>>>>>>>>> a >>>>>>>>>>>>>>>>> DAGs >>>>>>>>>>>>>>>>>>> UI >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-897] Prevent dagruns from failing with >>>> unfinished >>>>>>>>>>>>>>> tasks >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-861] make pickle_info endpoint be >>>> login_required >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-853] use utf8 encoding for stdout line = decode >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-856] Make sure execution date is set for = local >>>>>>>>>>>>>> client >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-830][AIRFLOW-829][AIRFLOW-88] Reduce = Travis >>>> log >>>>>>>>>>>>>>>> verbosity >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-794] Access DAGS_FOLDER and = SQL_ALCHEMY_CONN >>>>>>>>>>>>>>> exclusively >>>>>>>>>>>>>>>>>> from >>>>>>>>>>>>>>>>>>>>> settings >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-694] Fix config behaviour for empty = envvar >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-365] Set dag.fileloc explicitly and use = for >>>> Code >>>>>>>>>>>>>> view >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-931] Do not set QUEUED in TaskInstances >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-899] Tasks in SCHEDULED state should be = white >>>> in >>>>>>>>>>>>> the >>>>>>>>>>>>>>> UI >>>>>>>>>>>>>>>>>>> instead >>>>>>>>>>>>>>>>>>>>> of black >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-895] Address Apache release = incompliancies >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-893][AIRFLOW-510] Fix crashing webservers = when >>>> a >>>>>>>>>>>>>>> dagrun >>>>>>>>>>>>>>>>> has >>>>>>>>>>>>>>>>>> no >>>>>>>>>>>>>>>>>>>>> start date >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-793] Enable compressed loading in >>>>> S3ToHiveTransfer >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-863] Example DAGs should have recent = start >>>> dates >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-869] Refactor mark success functionality >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-856] Make sure execution date is set for = local >>>>>>>>>>>>>> client >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-814] Fix Presto*CheckOperator.__init__ >>>>>>>>>>>>>>>>>>>>> [AIRFLOW-844] Fix cgroups directory creation >>>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>>> No known issues anymore. >>>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>>> I would also like to raise a VOTE for releasing = 1.8.0 >>>>> based >>>>>>>>>>>>>> on >>>>>>>>>>>>>>>>>> release >>>>>>>>>>>>>>>>>>>>> candidate 5, i.e. just renaming release candidate = 5 to >>>>>>>>>>>>> 1.8.0 >>>>>>>>>>>>>>>>> release. >>>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>>> Please respond to this email by: >>>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>>> +1,0,-1 with *binding* if you are a PMC member or >>>>>>>>>>>>>> *non-binding* >>>>>>>>>>>>>>>> if >>>>>>>>>>>>>>>>>> you >>>>>>>>>>>>>>>>>>>> are >>>>>>>>>>>>>>>>>>>>> not. >>>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>>> Thanks! >>>>>>>>>>>>>>>>>>>>> Bolke >>>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>>> My VOTE: +1 (binding) >>>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> _/ >>>>>>>>>>>>>>>>> _/ Alex Van Boxel >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>>=20 >>>>>=20 >>>>=20 >>=20