Avoid logging empty line KPO

[pankajastro]

closes: #38105

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[hussein-awala]

Why do we need to filter empty log lines? From the reported issue, I see we have a problem with None, but IMHO we have to keep empty lines because the user may want to log them. WDYT?

(requested a change to avoid merging it before discussing the solution)

[pankajastro]

Why do we need to filter empty log lines? From the reported issue, I see we have a problem with None, but IMHO we have to keep empty lines because the user may want to log them. WDYT?

(requested a change to avoid merging it before discussing the solution)

I'm ok to change the check to None only.
2 logs I find a bit weird

1. INFO - [base] None i.e logging None. coming from pod_manager.py and in this case this log is unintentional
2. Container logs: i.e logging empty. coming from pod.py this also look unintentional

WDYT if I'll change pod_manager.py check to

if message_to_log is not None:

i.e just avoid printing None
And keep pod.py as it is in current form?

[pankajastro]

Hey @hussein-awala, would you like to review this one again? Thank you!

[anteverse]

Any updates on this? The last version seems to answer all problems and all demands.

[anteverse]

Thanks a lot!