You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "William Pursell (JIRA)" <ji...@apache.org> on 2017/10/21 05:27:00 UTC
[jira] [Commented] (AIRFLOW-1745) BashOperator ignores SIGPIPE in
subprocess
[ https://issues.apache.org/jira/browse/AIRFLOW-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213742#comment-16213742 ]
William Pursell commented on AIRFLOW-1745:
------------------------------------------
Also, see https://stackoverflow.com/questions/22077881/yes-reporting-error-with-subprocess-communicate and https://stackoverflow.com/questions/23064636/python-subprocess-popen-blocks-with-shell-and-pipe/23089677#23089677 It's not clear to me if signals other than SIGPIPE need be reset.
> 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
> 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)