gvergnolle opened a new issue, #57896:
URL: https://github.com/apache/airflow/issues/57896
### Apache Airflow version
3.1.1
### If "Other Airflow 2/3 version" selected, which one?
Actually 3.1.2, not available in the above dropdown
### What happened?
When the logs are of size ~100 lines, the log window is "cropped". As a
result, we can't see the logs.
### What you think should happen instead?
We can normally scroll through the logs of a task.
### How to reproduce
Here's a simple DAG:
```[python]
import logging
import pendulum
from airflow.sdk import (
task,
DAG,
)
logger = logging.getLogger(__name__)
logger.setLevel(logging.INFO)
N_LOGS = 100
with DAG(
dag_id="test_dag",
schedule=None,
start_date=pendulum.datetime(2025, 1, 1, tz="UTC"),
max_active_runs=1,
is_paused_upon_creation=False,
) as dag:
@task(dag=dag, task_id="print_stuff")
def print_stuff():
for i in range(N_LOGS):
logger.info(f"Processing item {i}")
print_stuff()
```
Try it with `N_LOGS=100`, and the window is significantly reduced. We can't
scroll to the first line (see video attached)
Try it with `N_LOGS=1000`, and all logs completely disappear (see
screenshot). I am scrolling in the void, and I can't make the logs appear.
<img width="1919" height="941" alt="Image"
src="https://github.com/user-attachments/assets/a3c9f3da-59f6-46d1-b109-5b2f6b9d9a89";
/>
https://github.com/user-attachments/assets/de7259d8-c15e-42ac-9da6-8196b25ff26d
### Operating System
Debian GNU/Linux 12 (bookworm)
### Versions of Apache Airflow Providers
apache-airflow-providers-standard==1.9.1
### Deployment
Docker-Compose
### Deployment details
_No response_
### Anything else?
I have observed the same behaviour with an `EcsRunTaskOperator`, so it may
affect **all** operator types, making it a significant issue.
### 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]
