Hey Elena, All,
Since we have solved some teething problems with Breeze I agreed with Elena
that we clearly separate out the two environments we have for Airflow -
Local Virtualenv and Breeze. I prepared a doc-only PR
https://github.com/apache/airflow/pull/6001 where advantages/disadvantages
of us
Hey Kevin,
Thanks for those - really helpful explanations! Sorry for spamming everyone
but I post answers here as maybe some people might find it useful for their
own usage of Breeze. I am also adding Elena - who is the technical writer
who started to work on onboarding documentation so that she c
Oh sry somehow I missed a detail there, it was the virtualenv use case
where I need to do the pip install. The docker approach went smoothily. I
recall two test cases where I need to install packages, one is from the gcp
operator tests and the other is a celery executor test( sry I can't
remember t
Fantastic. Thanks. Do you recall which tests/packages they were? I'd love
to see whats's the root cause. We are using the same image in CI and the
tests pass, so I wonder what could be the reason for that.
On Thu, Aug 29, 2019 at 4:13 AM Kevin Yang wrote:
> Was looking forward to this since last
Was looking forward to this since last meet up in bay area. Tried both the
docker solution and the virtualenv IDE( PyCharm) solution today and it was
great. Great job Jarek and thank you so much.
(One minor thing that may just be problem on my side: some tests complain
about missing package so I d
Great job Jarek! Thanks. I am looking forward to try it out as soon as I am
back from holiday :)
Felix
Sent from ProtonMail mobile
Original Message
On Aug 28, 2019, 10:34, Jarek Potiuk wrote:
> Just FYI. We had some "teething" problems (of course) at the workshop but
> fixes
Just FYI. We had some "teething" problems (of course) at the workshop but
fixes to it are already merged to master (thanks Kaxil for the review)!
J.
On Wed, Aug 28, 2019 at 2:17 AM Chao-Han Tsai wrote:
> Thanks Jarek for the hard work. It really improved the airflow development
> experience a l
Thanks Jarek for the hard work. It really improved the airflow development
experience a lot.
I remember the struggling I experienced to reproduce CI bug locally and I am
glad that those days are now gone. This really lowered the barrier to
contribute to Airflow and
I look forward to more people joi
Amazing! congrats and thank you.
On Tue, 27 Aug 2019 at 22:25, Jarek Potiuk wrote:
> Hello everyone,
>
> After a long time in the making I merged "Breeze" environment which is a
> swiss-knife of everything testing in Airflow. It should make it even easier
> to contribute to Airflow (easier to t
Hello everyone,
After a long time in the making I merged "Breeze" environment which is a
swiss-knife of everything testing in Airflow. It should make it even easier
to contribute to Airflow (easier to test your changes locally while
development in general).
There is a fairly comprehensive documen
10 matches
Mail list logo
