The GitHub Actions job "Tests (ARM)" on airflow.git/v3-3-test has failed. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 621af71add104a96f0d5678319020bb166466a70 / github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> [v3-3-test] Require Dag edit to delete asset queued events (#71736) (#71828) The three asset queued-events DELETE endpoints authorized the Dag axis with requires_access_dag(method="GET") — a read-level check — while deleting rows from AssetDagRunQueue, which cancels a Dag's pending asset-triggered scheduling. Every other Dag-scheduling mutation in the API requires Dag edit: Dag run clear, patch and delete use method="PUT"/"DELETE" with access_entity=RUN, and task-instance state changes use method="PUT". These three deletes were the only Dag-scheduling-state writes gated on read, so a caller holding delete on the global "Assets" resource plus only read on a Dag could suppress that Dag's asset-triggered runs. Change the Dag-axis gate on the three routes to method="PUT". The paired requires_access_asset(method="DELETE") and the ReadableDagsFilterDep row filter are unchanged; only the Dag axis moves from read to edit. The generated REST API permission reference is updated to match. The GET queued-events routes keep method="GET" — reading queued events is a read. Added a structural test asserting the Dag-axis method each queued-events route carries, so the read/write asymmetry cannot silently return. "dependant" is added to the spelling wordlist: it is FastAPI's own attribute name on a route. (cherry picked from commit 04145448135cfcc53644e8ca1a15fa188b129851) Generated-by: Claude Opus 5 (1M context) following the guidelines at https: //github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions Co-authored-by: Jarek Potiuk <[email protected]> Report URL: https://github.com/apache/airflow/actions/runs/32239836880 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
