airflow.task.raw points to airflow.task by default, which does have a handler and that is the one that is travelled. And yes we know the code is incorrect in this area, but the default does work correctly.
Bolke. > On 30 Nov 2017, at 16:27, Ash Berlin-Taylor <[email protected]> > wrote: > > Okay I think the problem (if not the cause) is around here: > https://github.com/apache/incubator-airflow/blob/master/airflow/bin/cli.py#L366-L376 > > > > log = logging.getLogger('airflow.task') > if args.raw: > log = logging.getLogger('airflow.task.raw') > > for handler in log.handlers: > try: > handler.set_context(ti) > except AttributeError: > # Not all handlers need to have context passed in so we ignore > # the error when handlers do not have set_context defined. > pass > > The problem seems to be that airflow.task.raw is no longer configured > explicitly, so it's log.handlers is an empty list. > > This in turn means that any log calls end up not writing anything as our > FileTaskHandler's self.handler property is None, meaning it doesn't emit > anything. > > Does this ring any bells to anyone? > > >> On 30 Nov 2017, at 15:18, Ash Berlin-Taylor <[email protected]> >> wrote: >> >> 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 >>> <[email protected]> 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 <[email protected]> wrote: >>>> >>>> Anyone else? Last day before I close the vote off. >>>> >>>> On Mon, Nov 27, 2017 at 12:32 PM, Driesprong, Fokko <[email protected]> >>>> wrote: >>>> >>>>> +1 >>>>> >>>>> Op ma 27 nov. 2017 om 21:24 schreef Bolke de Bruin <[email protected]> >>>>> >>>>>> +1, binding >>>>>> >>>>>> Let’s get it out! >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>>> On 27 Nov 2017, at 20:32, Chris Riccomini <[email protected]> >>>>> 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 >>>>>> >>>>> >>> >> >
