YoannAbriel opened a new pull request, #63387:
URL: https://github.com/apache/airflow/pull/63387
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
closes: #61676
-->
`ExecutionAPISecretsBackend.get_variable()` is missing the `RuntimeError` +
greenback fallback that `get_connection()` already has (added in #57154). When
a deferrable operator's trigger calls `Variable.get()` inside the triggerer's
async event loop, `SUPERVISOR_COMMS.send()` raises `RuntimeError` from
`async_to_sync`. The bare `except Exception` swallows it and returns `None`, so
every backend returns nothing and the variable is reported as not found.
Added the same greenback portal detection and `aget_variable()` fallback
that `get_connection()` uses. Added a matching unit test.
Closes: #61676
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Opus 4, claude-opus-4-6)
Generated-by: Claude Code (Opus 4, claude-opus-4-6) following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
