Skip to content

Stop a commented executable_resumable from marking a module durable - #73607

Merged
amoghrajesh merged 3 commits into
apache:mainfrom
astronomer:follow-up-registry-durable-pr
Oct 26, 2026
Merged

amoghrajesh merged 3 commits into
apache:mainfrom
astronomer:follow-up-registry-durable-pr

Conversation

@amoghrajesh

Copy link
Copy Markdown
Contributor

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

Follow-up to comments on #70298

The two capability walks disagreed about comments. The delegation walk strips them, on the grounds that a comment can say the opposite of what the code does, but the ResumableJobMixin walk searched raw source, so a comment naming execute_resumable was enough to earn the Durable badge.

The origin-resolution and depth-key rules in the deferral walk were both added to fix real misdetections, and both had no test that failed without them, so either could have been reverted as a simplification without anything noticing. The cases that need them are awkward to reach by accident: a helper the class under test overrides but an ancestor calls, and a helper reached first with too little depth budget left to finish the walk.

The four ModuleContract field tests asserted on the dict they passed in, which validate_modules_catalog returns unchanged, so they held even with the fields deleted from the model. They now assert through ModuleContract.model_validate.


  • Read the 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) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

Comment thread dev/registry/extract_parameters.py Resolved

@potiuk potiuk left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The branch doesn't allow edits from maintainers, so here are the open review points as suggestions you can apply directly. I ran dev/registry/tests/test_extract_parameters.py locally with all three applied: 95 passed. On the current head, the trailing-comment case still reports the operator as durable.


Drafted-by: Claude Code (Opus 5.5); reviewed by @potiuk before posting

Comment thread dev/registry/extract_parameters.py Resolved
@amoghrajesh amoghrajesh added the backport-to-v3-4-test Backport to v3-4-test label Oct 26, 2026
@amoghrajesh
amoghrajesh merged commit 77da6da into apache:main Oct 26, 2026
149 checks passed
@amoghrajesh
amoghrajesh deleted the follow-up-registry-durable-pr branch October 26, 2026 13:28
@github-project-automation github-project-automation Bot moved this from In progress to Done in Airflow Registry Oct 26, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Backport successfully created: v3-4-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
✅ v3-4-test PR Link

github-actions Bot pushed a commit to aws-mwaa/upstream-to-airflow that referenced this pull request Oct 26, 2026
…le durable (apache#73607)

(cherry picked from commit 77da6da)

Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
vatsrahul1001 pushed a commit that referenced this pull request Oct 26, 2026
…le durable (#73607) (#75660)

(cherry picked from commit 77da6da)

Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants