Hello,

For some people who are running airflow on prod with docker, this one is
quite important : https://issues.apache.org/jira/browse/AIRFLOW-1018. I
don't have log anymore :/

cheers,

On Fri, Mar 24, 2017 at 6:59 PM, Bolke de Bruin <[email protected]> wrote:

> Hi Chris
>
> I think some jira are missing from the blocker list, I'll supply them
> soon. Also some fixes are already in the v1-8-test branch, that are not
> part of your list yet and some need to be (check jira on fixes for 1.8.1).
>
> 982 and 983 might be fixed by reverting a change that we did as part of
> 1.8.0 and including the "wait for all tasks" patch, that is already in
> master. Let me pick this up.
>
> To help you out I already did some work on the jira classifications (e.g.
> try filtering on blocking issues) which should make it easier to find out
> what needs to go into 1.8.1.
>
> Bolke
>
> Sent from my iPhone
>
> > On 24 Mar 2017, at 10:21, Chris Riccomini <[email protected]> wrote:
> >
> > Hey all,
> >
> > I've let this thread sit for a while. Here are a list of the issues that
> > were raised:
> >
> > BLOCKERS:
> > https://issues.apache.org/jira/browse/AIRFLOW-982
> > https://issues.apache.org/jira/browse/AIRFLOW-983
> > https://issues.apache.org/jira/browse/AIRFLOW-1019
> > https://issues.apache.org/jira/browse/AIRFLOW-1017
> >
> > NICE TO HAVE:
> > https://issues.apache.org/jira/browse/AIRFLOW-1015
> > https://issues.apache.org/jira/browse/AIRFLOW-1013
> > https://issues.apache.org/jira/browse/AIRFLOW-1004
> > https://issues.apache.org/jira/browse/AIRFLOW-1003
> > https://issues.apache.org/jira/browse/AIRFLOW-1001
> >
> > It looks like AIRFLOW-1017 is done, though the JIRA is not closed.
> >
> > The rest remain open. I will wait on the release until the remaining
> > blockers are finished. Dan/Daniel, can you comment on status?
> >
> > Ruslan, if you want to work on your nice to haves, and submit patches,
> > that's great, otherwise I don't believe they'll get fixed as part of
> 1.8.1.
> >
> > Cheers,
> > Chris
> >
> > On Wed, Mar 22, 2017 at 9:19 AM, Ruslan Dautkhanov <[email protected]
> >
> > wrote:
> >
> >> Thank you Sid!
> >>
> >>
> >> Best regards,
> >> Ruslan
> >>
> >> On Wed, Mar 22, 2017 at 12:01 AM, siddharth anand <[email protected]>
> >> wrote:
> >>
> >>> Ruslan,
> >>> Thanks for sharing this list. I can pick a few up. I agree we should
> aim
> >> to
> >>> get some of them into 1.8.1.
> >>>
> >>> -s
> >>>
> >>> On Tue, Mar 21, 2017 at 2:29 PM, Ruslan Dautkhanov <
> [email protected]
> >>>
> >>> wrote:
> >>>
> >>>> Some of the issues I ran into while testing 1.8rc5 :
> >>>>
> >>>> https://issues.apache.org/jira/browse/AIRFLOW-1015
> >>>>> https://issues.apache.org/jira/browse/AIRFLOW-1013
> >>>>> https://issues.apache.org/jira/browse/AIRFLOW-1004
> >>>>> https://issues.apache.org/jira/browse/AIRFLOW-1003
> >>>>> https://issues.apache.org/jira/browse/AIRFLOW-1001
> >>>>> https://issues.apache.org/jira/browse/AIRFLOW-1015
> >>>>
> >>>>
> >>>> It would be great to have at least some of them fixed in 1.8.1.
> >>>>
> >>>> Thank you.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Ruslan Dautkhanov
> >>>>
> >>>> On Tue, Mar 21, 2017 at 3:02 PM, Dan Davydov <[email protected].
> >>>> invalid
> >>>>> wrote:
> >>>>
> >>>>> Here is my list for targeted 1.8.1 fixes:
> >>>>> https://issues.apache.org/jira/browse/AIRFLOW-982
> >>>>> https://issues.apache.org/jira/browse/AIRFLOW-983
> >>>>> https://issues.apache.org/jira/browse/AIRFLOW-1019 (and in general
> >> the
> >>>>> slow
> >>>>> startup time from this new logic of orphaned/reset task)
> >>>>> https://issues.apache.org/jira/browse/AIRFLOW-1017 (which I will
> >>>> hopefully
> >>>>> have a fix out for soon just finishing up tests)
> >>>>>
> >>>>> We are also hitting a new issue with subdags with rc5 that we weren't
> >>>>> hitting with rc4 where subdags will occasionally just hang (had to
> >> roll
> >>>>> back from rc5 to rc4), I'll try to spin up a JIRA for it soon which
> >>>> should
> >>>>> be on the list too.
> >>>>>
> >>>>>
> >>>>> On Tue, Mar 21, 2017 at 1:54 PM, Chris Riccomini <
> >>> [email protected]>
> >>>>> wrote:
> >>>>>
> >>>>>> Agreed. I'm looking for a list of checksums/JIRAs that we want in
> >> the
> >>>>>> bugfix release.
> >>>>>>
> >>>>>> On Tue, Mar 21, 2017 at 12:54 PM, Bolke de Bruin <
> >> [email protected]>
> >>>>>> wrote:
> >>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> On 21 Mar 2017, at 12:51, Bolke de Bruin <[email protected]>
> >>>> wrote:
> >>>>>>>>
> >>>>>>>> My suggestion, as we are using semantic versioning is:
> >>>>>>>>
> >>>>>>>> 1) no new features in the 1.8 branch
> >>>>>>>> 2) only bug fixes in the 1.8 branch
> >>>>>>>> 3) new features to land in 1.9
> >>>>>>>>
> >>>>>>>> This allows companies to
> >>>>>>>
> >>>>>>> Have a "known" version and can move to the new branch when they
> >>> want
> >>>> to
> >>>>>>> get new features. Obviously we only support N-1, so when 1.10
> >> comes
> >>>> out
> >>>>>> we
> >>>>>>> stop supporting 1.8.X.
> >>>>>>>
> >>>>>>>>
> >>>>>>>> Sent from my iPhone
> >>>>>>>>
> >>>>>>>>> On 21 Mar 2017, at 11:22, Chris Riccomini <
> >>> [email protected]>
> >>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> Hey all,
> >>>>>>>>>
> >>>>>>>>> I suggest that we start a 1.8.1 Airflow release now. The goal
> >>>> would
> >>>>>> be:
> >>>>>>>>>
> >>>>>>>>> 1) get a second release under our belt
> >>>>>>>>> 2) patch known issues with the 1.8.0 release
> >>>>>>>>>
> >>>>>>>>> I'm happy to run it, but I saw Maxime mentioning that Airbnb
> >>> might
> >>>>>> want
> >>>>>>> to.
> >>>>>>>>> @Max et al, can you comment?
> >>>>>>>>>
> >>>>>>>>> Also, can folks supply JIRAs for stuff that think needs to be
> >> in
> >>>> the
> >>>>>>> 1.8.1
> >>>>>>>>> bugfix release?
> >>>>>>>>>
> >>>>>>>>> Cheers,
> >>>>>>>>> Chris
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>



-- 

*Vincent Poulain*

Senior Software Engineer



Office +33 1 75 50 67 26 <+33%201%2075%2050%2067%2026> | Mobile +33 6 21 82
87 62 | [email protected] <[email protected]>

Tinyclues | 51 rue Étienne Marcel, 75001 Paris

www.tinyclues.com <http://bit.ly/2hNL4Fs> | @tinyclues
<https://twitter.com/Tinyclues>

Reply via email to