kaxil opened a new pull request, #73501: URL: https://github.com/apache/airflow/pull/73501
Follow-up to #73368 and #73450 from a backward-compatibility check of the released 0.9.0 provider against main. Every 0.9.0-style `LLMRetryPolicy` and `LLMBranchOperator` pattern from that release's docs was run against main's code with the model mocked, and each decision compared with the one 0.9.0 produced. Defaults are decision-for-decision identical on both surfaces. The check turned up a few small drifts that neither a test nor the changelog covered, fixed here: - A `fallback_rules` entry with `action=RetryAction.DEFAULT` lost its delay and reason on the fallback path. 0.9.0 returned the rule as written; a matched rule is now kept whatever its action, with the `LLM classification not applied (...)` prefix. - Passing `DEFAULT_INSTRUCTIONS`, or the documented `DEFAULT_INSTRUCTIONS + hints` shape, without `categories` raised the warning meant for 0.9.0 prompts that named their own categories and delays. The warning now skips a prompt that starts with the default. - An answer missing from `categories` surfaced as a swallowed `KeyError` traceback, and a subclass `_classify` returning something other than a `RetryDecision` was turned into a DEFAULT decision carrying the object's repr. Both now log what happened and take the fallback path as `model_error`. - `LLMOperator._push_decision` raised `AttributeError` when the context's `task_instance` was a plain dict, a shape older tests and hand-built runners use. It now warns and skips the push, as it already did when the key was missing. Docs: the changelog gains a note for the branching changes (`decision` XCom on every run, sorted option order, `branches` as a template field, generated enum member names) and one for the `decision` keyword `execute_complete` grew on four operators, which makes a subclass override with the old three-argument signature raise at resume. The branch guide gets the same "add an option for none of these" guidance the retry guide has, since a Choice settles which option fits best, not whether any does. -- 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]
