[jira] [Updated] (AIRFLOW-839) docker_operator.py attempts to log status key without first checking existence

[ https://issues.apache.org/jira/browse/AIRFLOW-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Perry updated AIRFLOW-839: --- Description: When pulling a docker image, docker_operator.py attempts to log the `status` key each

[jira] [Created] (AIRFLOW-839) docker_operator.py attempts to log status key without first checking existence

Mike Perry created AIRFLOW-839: -- Summary: docker_operator.py attempts to log status key without first checking existence Key: AIRFLOW-839 URL: https://issues.apache.org/jira/browse/AIRFLOW-839 Project:

[jira] [Updated] (AIRFLOW-839) docker_operator.py attempts to log status key without first checking existence

[ https://issues.apache.org/jira/browse/AIRFLOW-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Perry updated AIRFLOW-839: --- Description: When pulling a docker image, docker_operator.py attempts to log the `status` key each

[jira] [Updated] (AIRFLOW-839) docker_operator.py attempts to log status key without first checking existence

[ https://issues.apache.org/jira/browse/AIRFLOW-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Perry updated AIRFLOW-839: --- Priority: Minor (was: Trivial) > docker_operator.py attempts to log status key without first

[jira] [Commented] (AIRFLOW-366) SchedulerJob gets locked up when when child processes attempt to log to single file

[ https://issues.apache.org/jira/browse/AIRFLOW-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081168#comment-16081168 ] Mike Perry commented on AIRFLOW-366: [~bolke] we've been testing with this and seem to be in the