Closed jkramer-ginkgo closed 2 weeks ago
Duplicate of https://github.com/apache/airflow/pull/41605 fixed in https://github.com/apache/airflow/pull/41516 and available in 2.10.1rc1. Can you please double check if rc1 of 2.10.0 fixes the problem for you @jkramer-ginkgo - see https://github.com/apache/airflow/issues/41956 for links and details
Ideally pleasee comment in https://github.com/apache/airflow/issues/41956 when you confirm the problem is fixed.
@potiuk It is still broken in 2.10.1
.. I should've mentioned I had tested against a manually patched version with https://github.com/apache/airflow/pull/41605
@potiuk would you be able to reopen or should I dupe this issue?
Idealy copy it - this is easier for our "release" process.
@potiuk Cloned here: https://github.com/apache/airflow/issues/42117
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 https://github.com/apache/airflow/pull/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