potiuk opened a new pull request #21429:
URL: https://github.com/apache/airflow/pull/21429


   The fix from #21175 did not actually fix the logging behaviour
   with non-ascii characters returned by docker logs when xcom
   push was enabled. The problem is that DockerOperator uses
   different methods to stream the logs as they come (using attach
   stream) and different method to retrieve the logs to actually
   return the Xcom value. The latter uses "logs" method of docker
   client. The tests have not caught it, because the two methods
   were mocked in two different places.
   
   This PR uses the same "stringify()" function to convert both
   "logged" logs and those that are pushed as xcom.
   
   Fixes: #19027
   
   <!--
   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 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/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+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 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


-- 
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]


Reply via email to