alkismavridis opened a new issue, #58136: URL: https://github.com/apache/airflow/issues/58136
### Apache Airflow version 3.1.2 ### If "Other Airflow 2/3 version" selected, which one? _No response_ ### What happened? We use SSH Operators (wrapped inside a tiny PythonOperator wrapper). Naturally, our logs include messages from SSHHook. This unfortunatelly causes CSS-Positioning issues and our logs are not visible in the UI. Screenshot when SSHHook is not included (logs visible): <img width="937" height="528" alt="Image" src="https://github.com/user-attachments/assets/1a80f995-f064-4cee-bb31-599eb43ac70a"; /> Screenshot when SSHHook is included (either explicitly or via selecting "All Sources": <img width="997" height="583" alt="Image" src="https://github.com/user-attachments/assets/6b541e0b-25ef-4da4-b52c-8accfa64b46f"; /> I suspect that the issue has something to do with css positioning. The markdown is present, but shifted outside its viewbox. Manually removing the "height" property here makes the logs visible again: <img width="1445" height="715" alt="Image" src="https://github.com/user-attachments/assets/ecc85913-d3d5-43b0-8d4b-69e32adcd819"; /> ### What you think should happen instead? Logs should be visible. Not being able to read our logs is a pretty serious issue for us. ### How to reproduce - Execute a dag using SSHOperator. - Try to view the logs without excluding the SSHHook source ### Operating System MacOS (google chrome) ### Versions of Apache Airflow Providers _No response_ ### Deployment Docker-Compose ### Deployment details _No response_ ### 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]
