ashb opened a new pull request, #44064:
URL: https://github.com/apache/airflow/pull/44064
Under "normal" operation the subprocess will not do anything (other than a
few
imports) until it gets the StartupDetails message on stdin, but in our unit
tests
when we replace the target function with a custom implementation it's
possible
that the subprocess could exit (closing the stdin socket) before the parent
has written anything to it.
The fix is to make our test target follow the same behaviour of the real code
and read a line from stdin before doing anything else.
The error we say in tests was this:
```
________________ TestWatchedSubprocess.test_reading_from_pipes
_________________
[gw2] linux -- Python 3.9.20 /usr/local/bin/python
task_sdk/tests/execution_time/test_supervisor.py:72: in
test_reading_from_pipes
proc = WatchedSubprocess.start(
task_sdk/src/airflow/sdk/execution_time/supervisor.py:354: in start
feed_stdin.write(msg.model_dump_json().encode())
/usr/local/lib/python3.9/socket.py:734: in write
return self._sock.send(b)
E BrokenPipeError: [Errno 32] Broken pipe
```
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in a
newsfragment file, named `{pr_number}.significant.rst` or
`{issue_number}.significant.rst`, in
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
