YAshhh29 commented on PR #69812: URL: https://github.com/apache/airflow/pull/69812#issuecomment-5038961598
You're right that the UI isn't from main. The environment is Airflow **3.0.3** (a released core wheel), with my PR branch's `openai` provider installed on top of it. My PR only touches the `openai` provider (which is versioned independently and targets Airflow 3.x), so the core being 3.0.3 doesn't affect the `text_format` path — but I understand why the older UI raised a flag. Here's proof the running provider is this branch's code, not the released 1.8.0 (which has no `text_format`): <img width="1245" height="427" alt="Screenshot 2026-07-22 022218" src="https://github.com/user-attachments/assets/59687789-42d3-45a4-824a-e6a15cf8d91b"; /> So the feature itself genuinely ran on the branch code — the mismatch is only the core UI version, not the operator. That said, I'll redo the run against a **from-source main build** (core installed editable from the branch, not the 3.0.3 wheel) so the UI matches main and there's no ambiguity. I'll re-capture the Grid/logs/XCom on main's UI and update this thread shortly. --- -- 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]
