Hmmm is anyone else seeing logs from inside operators? Right now we're not 
getting any logs out of operators. I'm in the process of debugging to work out 
if it's our logging config or something in Airflow, but right now I don't seem 
to get any output from the operator itself, neither print(), or `ti.log.info()`

Anyone else noticed similar, or is it something specific to our environment?

-ash

> On 30 Nov 2017, at 09:52, Ash Berlin-Taylor <ash_airflowl...@firemirror.com> 
> wrote:
> 
> We're running more tests (day of meetings meant we couldn't do as many as I'd 
> have liked yesterday) but looking good so far.
> 
> +0.5 (non binding)
> 
> -ash
> 
>> On 29 Nov 2017, at 18:31, Chris Riccomini <criccom...@apache.org> wrote:
>> 
>> Anyone else? Last day before I close the vote off.
>> 
>> On Mon, Nov 27, 2017 at 12:32 PM, Driesprong, Fokko <fo...@driesprong.frl>
>> wrote:
>> 
>>> +1
>>> 
>>> Op ma 27 nov. 2017 om 21:24 schreef Bolke de Bruin <bdbr...@gmail.com>
>>> 
>>>> +1, binding
>>>> 
>>>> Let’s get it out!
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On 27 Nov 2017, at 20:32, Chris Riccomini <criccom...@apache.org>
>>> wrote:
>>>>> 
>>>>> Hey all,
>>>>> 
>>>>> I have cut Airflow 1.9.0 RC4. This email is calling a vote on the
>>>> release,
>>>>> which will last for 72 hours. Consider this my (binding) +1.
>>>>> 
>>>>> Airflow 1.9.0 RC4 is available at:
>>>>> 
>>>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.9.0rc4/
>>>>> 
>>>>> apache-airflow-1.9.0rc4+incubating-source.tar.gz is a source release
>>> that
>>>>> comes with INSTALL instructions.
>>>>> apache-airflow-1.9.0rc4+incubating-bin.tar.gz is the binary Python
>>>> "sdist"
>>>>> release.
>>>>> 
>>>>> Public keys are available at:
>>>>> 
>>>>> https://dist.apache.org/repos/dist/release/incubator/airflow/
>>>>> 
>>>>> The release contains the following JIRAs:
>>>>> 
>>>>> *https://issues.apache.org/jira/browse/AIRFLOW-1839
>>>>> <https://issues.apache.org/jira/browse/AIRFLOW-1839>*
>>>>> 
>>>>> Along with all JIRAs that were in 1.9.0RC3 (see previous VOTE email for
>>>>> full list).
>>>>> 
>>>>> Cheers,
>>>>> Chris
>>>> 
>>> 
> 

Reply via email to