When XCom value was null in DB, UI showed error:

With the changes in the PR, it now shows "null"

I propose we should backport this to 3.0-line as well.

Yeah, it is a bug-fix

@jscheffl the backport tool won't work post merge. Manual port will be required

@rawwar could you please create a manual backport?

@amoghrajesh did it already in #55095

I have a question regarding this fix, I am on airflow version 3.0.6 and using apache/airflow:slim-3.0.6-python3.11. I don't see this fix in that image. Is this not available in 3.0.6 or am I missing something?

EDIT: I see the fix in the changelog here in v3.1.0. Do I have to update to 3.1.0?

@prakharcode Yes, we do not backport bugfixes to older versions, it was fixed and merged for 3.1.0, you need to upgrade to benefit from this. (or cherry pick that patch and build your own airflow, but that's more effort)

Also seeing this on Airflow 3.0.6. AWS MWAA currently does not offer Airflow 3.1 Environments, so it's very unfortunate this bug fix cannot be applied for older versions.

Also seeing this on Airflow 3.0.6. AWS MWAA currently does not offer Airflow 3.1 Environments, so it's very unfortunate this bug fix cannot be applied for older versions.

It can be. Those who run managed service can backport any change to their versions. This is open source and people work here mostly as volunteers and you get what you pay for - i.e. you pay 0 to airflow community and you pay maintenance fee to whoever you bought managed service frome.

It seems pretty eggregious to demand people who work for free to do something to do "extra effort" rather than those who get money for maintenace. I guess you should be demanding more from those who your money are directed to, rather than those who you paid exactly 0. @emilsauer .

Or am I missing something?

Also seeing this on Airflow 3.0.6. AWS MWAA currently does not offer Airflow 3.1 Environments, so it's very unfortunate this bug fix cannot be applied for older versions.

It can be. Those who run managed service can backport any change to their versions. This is open source and people work here mostly as volunteers and you get what you pay for - i.e. you pay 0 to airflow community and you pay maintenance fee to whoever you bought managed service frome.

It seems pretty eggregious to demand people who work for free to do something to do "extra effort" rather than those who get money for maintenace. I guess you should be demanding more from those who your money are directed to, rather than those who you paid exactly 0. @emilsauer .

Or am I missing something?

I appreciate the context. I think there was a misunderstanding of my intent. I certainly wasn't demanding a backport or suggesting extra effort from the community.

My comment was meant to document that the issue persists in 3.0.6 for the benefit of other users who, like me, are currently restricted to that version. Since this bug is not trivial to diagnose, I wanted to provide a reference point for others to share findings or workarounds. I just wanted to clarify my intent here. Thanks for the work on the project.