YAshhh29 commented on PR #69812: URL: https://github.com/apache/airflow/pull/69812#issuecomment-5039564087
The earlier run was on 3.0.3 core (was pre-installed in my Codespace) with the branch openai provider on top, which is why the UI looked older. That combo still exercised the change, but you're right that it wasn't the right proof. I re-ran the smoke DAG on Airflow 3.4.0 from source (main) with the openai provider from this branch, in a clean AIRFLOW_HOME. Same DAG — extract Person(name: str, age: int) from "Alice is 30 years old." — hits the real OpenAI Responses API. Screenshots include: 1. Grid — extract_person finished green in ~6s, one try, OpenAIResponseOperator 2. Logs — Generated response resp_0eb37e37… from airflow.providers.openai.operators.openai.OpenAIResponseOperator, followed by the XCom push 3. XCom — return_value key present at the run's end timestamp 4. Terminal — same Generated response resp_… line pulled from the log file Happy to add a second smoke case (validation-failure branch, or the dict-fallback in parse_response) if you want that covered too — just say the word. <img width="1841" height="552" alt="Screenshot 2026-07-22 033030" src="https://github.com/user-attachments/assets/20918dea-4c4e-4a14-8705-7ecf4f48e3ca"; /> <img width="745" height="107" alt="Screenshot 2026-07-22 033445" src="https://github.com/user-attachments/assets/11791647-5afc-4e91-b14f-b3ce06c6e922"; /> <img width="1451" height="416" alt="Screenshot 2026-07-22 032803" src="https://github.com/user-attachments/assets/32f5641e-d39f-4c86-95e4-7a2943e52338"; /> <img width="747" height="105" alt="image" src="https://github.com/user-attachments/assets/589c2c1e-fa14-4b77-950f-fa50c7273079"; /> <img width="1471" height="527" alt="image" src="https://github.com/user-attachments/assets/f53e1525-37d2-44d2-87cc-4463070bb658"; /> -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
