pierrejeambrun opened a new pull request, #67846:
URL: https://github.com/apache/airflow/pull/67846

   Wires the Dag Runs bulk-clear action to the new `POST 
/dags/{dag_id}/clearDagRuns` bulk endpoint, replacing the previous client-side 
fan-out that issued one single-run clear request per selected run.
   
   - `useBulkClearDagRuns` now makes a single atomic `clearDagRuns` call (`~` 
wildcard, each entry carries its own `dag_id`) instead of `Promise.allSettled` 
over per-run calls.
   - `useBulkClearDagRunsDryRun` now makes a single dry-run call instead of a 
`useQueries` fan-out.
   - `BulkClearDagRunsButton` is unchanged — both hooks keep their signatures 
and return shapes.
   
   **Behavior change:** the bulk clear is now **atomic** — all selected runs 
clear or none do. The previous fan-out allowed partial success (clear the runs 
that succeed, report per-run errors). This aligns dag-run bulk clear with the 
existing `post_clear_task_instances` endpoint, which is already a single 
all-or-nothing transaction. On failure the dialog stays open and shows a single 
request-level error.
   
   Depends on #67709 (the bulk endpoint + regenerated client live on that 
branch). This PR is stacked on it — until #67709 merges, the diff here also 
shows #67709's commits; the UI change itself is the single commit "UI: Use bulk 
clearDagRuns endpoint instead of per-run fan-out".
   
   Screenshots (to be added):
   - Bulk clear dialog — default (existing tasks)
   - Options toggled (only failed / queue new)
   - Success toast after clear
   - Error state (request-level failure)
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 4.8)
   
   Generated-by: Claude Code (Opus 4.8) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
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]

Reply via email to