You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "kaxil (via GitHub)" <gi...@apache.org> on 2026/10/01 23:55:43 UTC

Re: [PR] Fix XCom get_value outside task runner [airflow]

kaxil commented on PR #68789:
URL: https://github.com/apache/airflow/pull/68789#issuecomment-5942944184

   Does this need new API on `XComModel`? On #59093 the problem was using the Task SDK `XCom` in API-server code, and the existing `XComModel.get_many(...)` covers reading XComs there. `get_one` also calls `deserialize_value` on the result, which `operatorlink.py` deliberately avoids in the same API-server context because it "could instantiate arbitrary classes from untrusted XCom data". Exporting the server ORM model through `common.compat.sdk` mixes server and task imports in one module. Is there a case `get_many` doesn't cover? Converting to draft until there is.
   


-- 
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-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org