Thanks for the input! I'll take a look at using queues for this.
thanks,
Dennis
On Tue, Jan 30, 2018 at 4:17 PM Hbw wrote:
> Run them on different workers by using queues?
> That way different workers can have different 3rd party libs while sharing
> the same
Same here - I still have a couple outstanding tickets re: documentation for
2.0, would be helpful if I had additional access
- Andy
> On Feb 4, 2018, at 12:07 PM, Naik Kaxil wrote:
>
> Happy to pick it up if permitted.
>
> Regards,
> Kaxil
>
> On 04/02/2018, 16:14, "Bolke
Happy to pick it up if permitted.
Regards,
Kaxil
On 04/02/2018, 16:14, "Bolke de Bruin" wrote:
Perfectly fine to me. It would be highly appreciated if this could be
picked up so it can be made opart of the release process.
@Arthur @max: can you share / make
Perfectly fine to me. It would be highly appreciated if this could be picked up
so it can be made opart of the release process.
@Arthur @max: can you share / make available credentials?
Cheers
Bolke
> On 4 Feb 2018, at 15:16, Naik Kaxil wrote:
>
> Yes, the same happened to
Yes, the same happened to me. One of my colleague wanted to use a Google Cloud
Storage operator but he was looking at the old docs so he couldn't find one.
I suggest we should have documentation at 2 places:
1) PythonHosted - For latest stable airflow version on PyPI
2) Readthedocs - For
This is a good question, I see that artwr and Maxime are owners of the
project, maybe they can fix the build? Or add some more Airflow committers
as readthedocs project owners.
I get quite some questions from colleagues because they are reading old
docs :)
Cheers, Fokko
2018-02-04 14:32
Hi guys,
Are we still using http://airflow.readthedocs.io/ for latest documentation?
I see that the last build was 2 months ago which failed..
http://readthedocs.org/projects/airflow/builds/
The documentation at http://pythonhosted.org/airflow/ will only be for the
latest airflow version at