wrong display of multiline messages in the log after filtering by message level

[Pad71]

Apache Airflow version

2.9.3

If "Other Airflow 2 version" selected, which one?

No response

What happened?

Problem displaying an error in the tab Logs in the task detail.

If the error text in the log is on multiple lines, it is displayed correctly in the basic view without filtering (see the picture)

But if I use filter by message level (e.g. error, see the pict) , then only the first line of the same error message is displayed. The information on the other lines for this error message is not visible (see the picture)

What you think should happen instead?

A multi-line message should be displayed in its entirety even after applying the message level filter

How to reproduce

Display a multi-line message (typically an error message) in the task log and then apply a filter to the ERROR level

Operating System

Linux

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

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

• I agree to follow this project's Code of Conduct

[Pad71]

the same problem with displaying multiline message is also when filtering to other levels (e.g. INFO etc.)

[Lee-W]

Thanks for reporting this. I just verified this happens in the latest main (45658a8963761ce8a565b481156c847e493fce67)

[Lee-W]

cc @bbovenzi

[bbovenzi]

Talking with Ash about his TaskSDK work. Logs will be sent to the UI in json format so we won't need all of this regex string processing to try to add features to logs. But this is important enough to fix for 2.10.x or 2.11

[jason810496]

Hi @Lee-W, I could try resolve this issue, could you assign to me, thanks !

[Lee-W]

Hi @Lee-W, I could try resolve this issue, could you assign to me, thanks !

Definitely, just assigned it to you 🙂

[jason810496]

Hi @Lee-W, I think this issue can be close since the PR has been merged, thanks 🙌

[Lee-W]

Sure. Thanks for reminding me 🙂 Next time, you can mention close: #pr-number in your pr, and it'll automatically close the issue