Woooho!
On Tue, Nov 10, 2020 at 12:00 AM Ash Berlin-Taylor wrote:
> I'm proud to announce the availability of Apache Airlow 2.0.0.beta1 for
> testing.
>
> This now marks us being "feature complete" for core Airflow -- from now on
> any significant new features to core Airflow will have to wait u
I'm proud to announce the availability of Apache Airlow 2.0.0.beta1 for testing.
This now marks us being "feature complete" for core Airflow -- from now on any
significant new features to core Airflow will have to wait until 2.1 -- but
thanks to the split out of provider packages those can conti
Hi all,
I would like to remind whoever is interested in helping in Airflow 2.0
Release process that we will have our weekly developer call today:
*Airflow 2.0 Dev Call Calendar Link*:
https://calendar.google.com/calendar/embed?src=c_dhdh3bdjc42c4ngtnpg7ovcs9g%40group.calendar.google.com&ctz=Europ
I would say let's just run it against master, not even v1-10-test
On Mon, Nov 9, 2020 at 12:33 PM Jarek Potiuk
wrote:
> Hello everyone,
>
> I have not seen a single time any security Analysis job Code QL would
> produce any valuable output. I've seen it failing for no reason a few times
> though
Sounds good to me.
I haven't tested any other providers yet, but consider by -0 vote retracted.
-ash
On Nov 9 2020, at 4:00 pm, Jarek Potiuk wrote:
> Cool. happy to release backports for those packages after current voting ends.
>
> It's now rather easy and takes very little time to prepare it an
Cool. happy to release backports for those packages after current voting
ends.
It's now rather easy and takes very little time to prepare it and we got
into the "release as needed" schedule.
J.
On Mon, Nov 9, 2020 at 4:30 PM Ash Berlin-Taylor wrote:
> PR to fix it https://github.com/apache/a
PR to fix it https://github.com/apache/airflow/pull/12200
-ash
On Nov 9 2020, at 2:56 pm, Ash Berlin-Taylor wrote:
> Mostly -- the batch_waiters.json for Amazon was the one that wasn't.
>
> On Nov 9 2020, at 2:50 pm, Jarek Potiuk wrote:
> > Indeed. Those were mostly examples, but it's good to hav
Mostly -- the batch_waiters.json for Amazon was the one that wasn't.
On Nov 9 2020, at 2:50 pm, Jarek Potiuk wrote:
> Indeed. Those were mostly examples, but it's good to have them :D. Thanks for
> catching this!
>
> J.
>
>
> On Mon, Nov 9, 2020 at 3:40 PM Ash Berlin-Taylor (mailto:a...@apache.
Indeed. Those were mostly examples, but it's good to have them :D. Thanks
for catching this!
J.
On Mon, Nov 9, 2020 at 3:40 PM Ash Berlin-Taylor wrote:
> -0 -- it turns out that we are missing data files in the packages!
> https://github.com/apache/airflow/issues/12197
> (-0 but not blocking,
-0 -- it turns out that we are missing data files in the packages!
https://github.com/apache/airflow/issues/12197
(-0 but not blocking, as this has probably been the case for a all previous
backport providers we have released.)
Fix coming soon anyway.
-ash
On Nov 9 2020, at 2:12 pm, Jarek Potiuk
Hey all,
I have cut Airflow Backport Providers 2020.11.13rc1. This email is calling
a vote on the release,
which will last for 72 hours - which means that it will end on Thu, 12th of
Nov 2020, 3 pm CET.
Consider this my (binding) +1.
Airflow Backport Providers 2020.11.13rc1 are available at:
htt
Hello everyone,
I have not seen a single time any security Analysis job Code QL would
produce any valuable output. I've seen it failing for no reason a few times
though. And the Python analysis takes 20 minutes of build-job time. And it
adds some complexity into cancelling duplicate jobs.
We've d
Hi all,
How could I kill a running task instance of airflow ?Is there any api can
be invoked to kill a running task instance for a java web app?
Many thanks for your general help!
Cool stuff. It looks like we have some nice incremental steps that we can
start introducing.
Just a comment after the meeting - my current thinking about the triage
process improvement. As I understand the approach you propose now is that
rather than trying to define the whole triage process up-fr
14 matches
Mail list logo
