Yes I think so.
Bolke
Sent from my iPhone
> On 1 Aug 2017, at 00:59, Maxime Beauchemin wrote:
>
> Alright so here's the INSTALL file:
> https://github.com/apache/incubator-airflow/pull/2492
>
> I'm thinking I'll cherry pick this in the 1.8-test branch and tar the
I need to re-package it with build instructions. I'm pretty sure this means
another vote. I have time carved up to work on this today/tomorrow.
Max
On Thu, Jul 27, 2017 at 9:18 AM, Chris Riccomini
wrote:
> IMO, given the level of effort for 1.8.2, and how long it's
IMO, given the level of effort for 1.8.2, and how long it's taken, we
should not be re-voting right now unless something horrific happened to the
release.
On Tue, Jul 25, 2017 at 9:54 PM, Pavel Martynov wrote:
> Hi, folks!
>
> AIRFLOW-935 issue marked as resolved and fix
Hi, folks!
AIRFLOW-935 issue marked as resolved and fix version is 1.8.2, but this
commit contained in master branch only and not tagged by 1.8.2rc2.
Can fix of this issue be released in 1.8.2?
2017-07-26 2:27 GMT+03:00 George Leslie-Waksman <
geo...@cloverhealth.com.invalid>:
> I've checked
I've checked and we are no longer relying on the previous
LatestOnlyOperator behavior for any of our DAGs.
This is not a dealbreaker (though I will need to keep it in mind).
Thanks for asking,
--George
On Tue, Jul 25, 2017 at 2:50 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:
>
I hope that it's not too late for me to chime in but there is a breaking
change in the behavior of LatestOnlyOperator.
The change was introduced in
PR: https://github.com/apache/incubator-airflow/pull/2365
Change: 333e0b3 [AIRFLOW-1296] Propagate SKIPPED to all downstream tasks
Prior to this
I think I'm gathering a good picture of what is expected here. I'll try to
update the Confluence page as I go.
I'm hoping to get started tomorrow and package it early next week.
Max
On Wed, Jul 19, 2017 at 6:16 PM, siddharth anand wrote:
> FYI, can anyone pictorially
FYI, can anyone pictorially describe the release process (and post it on
the apache airflow wiki)? I think that would eliminate a lot of confusion
in the future and avoid a rehash of this email thread on the next release.
-s
On Wed, Jul 19, 2017 at 10:48 AM, Hitesh Shah
To add, the main source tarball should have instructions to generate the
sdist and bdist versions. Additionally, as part of the release process if
the plan is to publish to pypi (after the IPMC vote succeeds), then the
appropriate bits also need to be verified/voted upon. There are not exactly
Thanks Hitesh. We discussed it with John Ament on the IPMC. Python has the
notion of 3 types of distributions, “source”, “sdist”, “bdist”, contrary to
Java that knows only two (source, bdist). We used to vote on “sdist”, which was
deemed incorrect.
So, Max, indeed we need to vote on a tar.gz
Great!
It is also a bit new to me so maybe @Hitesh @Jakob can help with some guidance
here?
But my assumption indeed is:
1. Make a tarball from the repo with build instructions (including a working
License check!) -> Vote here and IPMC. This is the “official” release.
2. Make sdist for
Max, Ping? Do you need help?
> On 9 Jul 2017, at 14:30, Bolke de Bruin wrote:
>
> Hi Max,
>
> The canonical distribution would be what we have in git right now (ie. before
> running python sdist). The rest is just convenience packages. So npm, would
> solve the issue as
Hi Max,
The canonical distribution would be what we have in git right now (ie. before
running python sdist). The rest is just convenience packages. So npm, would
solve the issue as long as we don’t rely on any non APL compatible packages in
core. I don’t think npm/yarn/webpack needs to be done
Hi Folks,
We probably need to adjust our release process as can be observed in the IPMC
thread. As we are packaging a “sdist” it does not pass license checks and one
cannot verify the validity of what we are doing. It was suggested by one of the
maintainers of another python project to create
Awesome.. thanks a lot Max for taking the RM responsibility..
On Jul 5, 2017 11:10 PM, "Chris Riccomini" wrote:
> Nice, thanks Max!
>
> On Mon, Jul 3, 2017 at 2:36 PM, Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Hello,
> >
> > Apache Airflow
Hello,
Apache Airflow (incubating) 1.8.2 (RC2) has been accepted.
5 “+1” votes received, 4 out of which are "binding":
- Maxime Beauchemin (binding)
- Bolke de Bruin (binding)
- Chris Riccomini (binding)
- Sumit Maheshwari (binding)
- Kengo Seki (non-binding)
Vote thread (start):
Max,
I think you can close the vote?
Bolke
> On 27 Jun 2017, at 02:45, Kengo Seki wrote:
>
> +1 (non-binding)
>
> - verified signatures and checksums
> - ran scheduler and webserver, confirmed they worked fine
> - confirmed the latest fix on v1.8 branch (AIRFLOW-809) is
+1 (non-binding)
- verified signatures and checksums
- ran scheduler and webserver, confirmed they worked fine
- confirmed the latest fix on v1.8 branch (AIRFLOW-809) is included
Kengo Seki
2017-06-27 8:53 GMT+09:00 Chris Riccomini :
> +1 (binding)
>
+1 (binding)
Been running in our dev env, and everything looks good.
On Mon, Jun 26, 2017 at 3:00 PM, Alex Guziel wrote:
> Yeah that makes sense. It pages by default at 500 so it explains why we saw
> it.
>
> On Mon, Jun 26, 2017 at 2:53 PM, Chris Riccomini
Yeah that makes sense. It pages by default at 500 so it explains why we saw
it.
On Mon, Jun 26, 2017 at 2:53 PM, Chris Riccomini
wrote:
> In 1.8.1, the "DAGs" page has "Show entries". In 1.8.2, it has
> "Show <25> entries". So it looks like prior to 1.8.2, the pagination
In 1.8.1, the "DAGs" page has "Show entries". In 1.8.2, it has
"Show <25> entries". So it looks like prior to 1.8.2, the pagination was
broken in the sense that it defaulted to the whole list. We have 479 DAGs
in one env, and it shows them all. It looks like someone fixed the entry to
default to
We're running 1.8.0 + some extras, and none of us added pagination
recently, and our homepage is paginated. Are you sure it's not the number
of dags crossing the threshold? Maybe it's some Flask version thing?
On Mon, Jun 26, 2017 at 2:45 PM, Chris Riccomini
wrote:
> Yes,
Also, still see `airflow.exceptions.AirflowConfigException: section/key
[celery/celery_ssl_active] not found in config` when running with celery
executor. Likely this PR fixes,
https://github.com/apache/incubator-airflow/pull/2341, but it needs rebase
to try to pass tests.
On Mon, Jun 26, 2017 at
Yes, I did the 1.8.1 release.
On Mon, Jun 26, 2017 at 2:44 PM, Alex Guziel wrote:
> There's no pagination in 1.8.1? Are you sure?
>
> On Mon, Jun 26, 2017 at 2:37 PM, Chris Riccomini
> wrote:
>
> > It's not happening on 1.8.1 (since
There's no pagination in 1.8.1? Are you sure?
On Mon, Jun 26, 2017 at 2:37 PM, Chris Riccomini
wrote:
> It's not happening on 1.8.1 (since there's no pagination in that version),
> so I'd count this as a regression. I wouldn't say it's blocking, but it's
> pretty ugly.
>
I'm not so sure this is a new issue. I think we've seen it on our
production for quite a while.
On Mon, Jun 26, 2017 at 2:31 PM, Chris Riccomini
wrote:
> I am seeing a strange UI behavior on 1.8.2.RC2. I've opened a JIRA here:
>
>
I am seeing a strange UI behavior on 1.8.2.RC2. I've opened a JIRA here:
https://issues.apache.org/jira/browse/AIRFLOW-1348
Has anyone else seen this?
On Mon, Jun 26, 2017 at 3:27 AM, Sumit Maheshwari
wrote:
> +1, binding.
>
>
> On Mon, Jun 26, 2017 at 3:49 PM, Bolke
+1, binding.
On Mon, Jun 26, 2017 at 3:49 PM, Bolke de Bruin wrote:
> We have been running it for the last couple of days. No issues and seems
> more responsive.
>
> +1, binding
>
> Bolke
>
> > On 25 Jun 2017, at 01:10, Maxime Beauchemin
> wrote:
We have been running it for the last couple of days. No issues and seems more
responsive.
+1, binding
Bolke
> On 25 Jun 2017, at 01:10, Maxime Beauchemin
> wrote:
>
> Dear all,
>
> 1.8.2 RC2 is baked and available at:
>
Dear all,
1.8.2 RC2 is baked and available at:
https://dist.apache.org/repos/dist/dev/incubator/airflow, public keys
are available
at https://dist.apache.org/repos/dist/release/incubator/airflow.
Note that RC1 was the first RC (skipped RC0) and was never announced since
it had issues coming out
30 matches
Mail list logo