Xcom view broken for non-JSON values #41981
Labels
area:core
area:UI
Related to UI/UX. For Frontend Developers.
duplicate
Issue that is duplicated
kind:bug
This is a clearly a bug
needs-triage
label for new issues that we didn't triage yet
Apache Airflow version
2.10.0
If "Other Airflow 2 version" selected, which one?
No response
What happened?
Non-JSON values are broken in the Xcom UI [screenshot attached]
Root cause is this line from #40640. Setting
stringify: false
results in JSON encoding which results inTypeError: keys must be str, int, float, bool or None, not tuple
exception fromGET <Airflow URL>/api/v1/dags/<DAG>/dagRuns/<Run ID>/taskInstances/<Task ID>/xcomEntries/<Xcom name>?stringify=false
endpoint.The PR's intention is to make the whole view JSON, so not sure if the intention is to error on non-JSON Xcom values, or if it should be updated to have clean fallback logic.
What you think should happen instead?
No response
How to reproduce
Create Xcom value that is non-JSON serializable (e.g.
{('201009_NB502104_0421_AHJY23BGXG (SEQ_WF: 138898)', None): 82359}
) and then try to view in UI Xcom tabOperating System
Linux (Ubuntu 22.04)
Versions of Apache Airflow Providers
No response
Deployment
Virtualenv installation
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: