danielford831 opened a new issue, #58226:
URL: https://github.com/apache/airflow/issues/58226

   ### Apache Airflow version
   
   3.1.2
   
   ### If "Other Airflow 2/3 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   When logging a relatively small amount of data (in this example, JSON 
records) then UI logs seem to have visual issues after about 50 lines
   
   <img width="1083" height="499" alt="Image" 
src="https://github.com/user-attachments/assets/c2b68de6-df1f-442b-a868-b2bc22e42526";
 />
   
   https://youtu.be/s7kJTNeSjHQ
   
   ^^ Video of the observed behaviour.
   
   This has been introduced somewhere between 3.0.6 and 3.1.2 which we upgraded 
to this week.
   
   NOTE: The logs are downloadable from the UI and we are using remote logging 
to S3 for task logs, but this appears to be a front-end issue so that SHOULDNT 
matter
   
   ### What you think should happen instead?
   
   The logs should be readable from the UI.
   
   ### How to reproduce
   
   Tiny reproducible setup used for the Youtube video above
   
   
[json_logging_test.py](https://github.com/user-attachments/files/23496314/json_logging_test.py)
   
   Run this in airflow -- we personally see the output start to "freak out" in 
every single task, but it gets worse as the number of lines printed progresses. 
Past 200 its completley invisible.
   
   ### Operating System
   
   MacOS
   
   ### Versions of Apache Airflow Providers
   
   default providers for 3.1.2
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   EKS
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] 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