[
https://issues.apache.org/jira/browse/AIRFLOW-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213811#comment-16213811
]
ASF subversion and git services commented on AIRFLOW-1745:
----------------------------------------------------------
Commit ca961042c146d49504e00e4abefc7779f0747782 in incubator-airflow's branch
refs/heads/master from [~wrp]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=ca96104 ]
[AIRFLOW-1745] Restore default signal disposition
Restore defaults for SIGPIPE, SIGXFZ, and SIGXFSZ
Python 2.7 subprocess resets signal disposition
for these
signals to ignore, which can cause problems. For
example,
a simple BashOperator executing 'yes | head' may
never
terminate. For details, see discussion at:
https://bugs.python.org/issue1652
https://stackoverflow.com/questions/22077881/yes-
reporting-error-with-subprocess-communicate
etc.
Closes #2714 from wrp/sigpipe
> BashOperator ignores SIGPIPE in subprocess
> ------------------------------------------
>
> Key: AIRFLOW-1745
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1745
> Project: Apache Airflow
> Issue Type: Bug
> Components: DagRun
> Affects Versions: Airflow 1.8
> Reporter: William Pursell
> Assignee: William Pursell
> Fix For: 1.9.0
>
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> In Python 2, subprocesses ignore SIGPIPE (https://bugs.python.org/issue1652).
> As a result, a simple bash operator with bash_command = 'yes | head' may
> never terminate (depending on the implementation of yes). Airflow should
> reset the signal disposition to default.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
