notatallshaw-gts opened a new issue, #58911:
URL: https://github.com/apache/airflow/issues/58911

   ### Apache Airflow version
   
   2.11.0
   
   ### If "Other Airflow 2/3 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   This is a follow up to https://github.com/apache/airflow/issues/33692, which 
was only partially fixed by the submitted PR 
https://github.com/apache/airflow/pull/43840
   
   I just upgraded to Airflow 2.11.0, removed my internal patch to fix log 
formatting, but now I see errors like this:
   
   ```
   [2025-11-30, 23:00:57 EST] {docker.py:66} INFO -   File 
".../.venv/lib/python3.12/site-packages/click/core.py", line 814, in invoke
   [2025-11-30, 23:00:57 EST] {docker.py:66} INFO -     return callback(*args, 
**kwargs)
   [2025-11-30, 23:00:57 EST] {docker.py:66} INFO -            ^^^^^^^^^
   [2025-11-30, 23:00:57 EST] {docker.py:66} INFO - ^^^^^^^^^^^^^^^
   [2025-11-30, 23:00:57 EST] {docker.py:66} INFO - ^
   ```
   
   ### What you think should happen instead?
   
   The code should more carefully track chunks, it could receive midline splits 
like this:
   
   ```python
   [
       b"    rv = self.invoke(ctx)\n         ^^^",  # Note: no trailing 
newline, splits the carets
       b"^^^^^^^^^^^^^\n",  # Continuation of previous line
   ]
   ```
   
   ### How to reproduce
   
   Have an exception when using Docker Operator.
   
   ### Operating System
   
   Linux
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-docker==4.4.3
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   Celery + Redis + Docker Swarm
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.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