jkramer-ginkgo opened a new issue, #41981: URL: https://github.com/apache/airflow/issues/41981
### 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](https://github.com/jscheffl/airflow/blob/5f5039a6531d9366ac7ffc9a05492b7a93bc8f87/airflow/www/static/js/api/useTaskXcom.ts#L66) from https://github.com/apache/airflow/pull/40640. Setting `stringify: false` results in JSON encoding which results in `TypeError: keys must be str, int, float, bool or None, not tuple` exception from `GET <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 tab ### Operating 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? - [ ] 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: commits-unsubscr...@airflow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
