Lohith625 commented on issue #58553:
URL: https://github.com/apache/airflow/issues/58553#issuecomment-3675368997
Hi @melicheradam and @mbielejeski, thanks for the detailed reports and
apologies for the delayed update on my side.
I tested the exact DAG shared by @mbielejeski locally on `Airflow 3.1.3
running inside WSL (Linux) on a Windows host`, accessed via Chrome, and I’m
seeing slightly different behavior on my setup.
With the provided example:
```
for i in range(0, 100):
log.info(f"[Iteration {i}]: Doing some work")
```
I can scroll all the way to the top and see the logs starting from
[Iteration 0], and when scrolling to the bottom I can also see the final
iterations (up to [Iteration 99]) without missing entries. I’ve attached
screenshots showing both the top and bottom of the log view from my local run.
That said, I do see that in your screenshots the visible range is truncated
(starting around iteration ~33 at the top and ending ~76 at the bottom), which
I’m currently unable to reproduce on my machine. This makes me wonder if the
behavior could be browser- or platform-specific (e.g. Firefox vs Chrome, or
macOS vs Linux), or related to subtle layout differences.
@melicheradam — yes, I can confirm that I’m also observing the same behavior
you mentioned. In my local setup, the logs do start from line 2 instead of 1,
even when scrolling fully to the top. I’ve attached screenshots showing this
behavior from my environment as well.
- Log view when scrolled to the top
<img width="1920" height="918" alt="Image"
src="https://github.com/user-attachments/assets/167dfb08-9893-4e87-900b-b93afbc53e10";
/>
- Log view when scrolled to the bottom
<img width="1920" height="914" alt="Image"
src="https://github.com/user-attachments/assets/af4b47fa-df3d-4d8e-a14f-9ebd64dbb0c3";
/>
So at the moment, my understanding is:
- The log numbering offset (starting from 2) is reproducible on my side and
looks like a real issue.
- The scroll range truncation (missing top/bottom iterations) seems
environment- or browser-dependent, and I haven’t been able to reproduce it
locally yet.
I’m happy to investigate the log numbering issue further, and also take a
look at the UI/layout side (e.g. how the log container height is computed) if
you think both behaviors should be addressed together. Please let me know how
you’d like me to proceed.
--
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]
