BaconMan1168 commented on issue #71948: URL: https://github.com/apache/airflow/issues/71948#issuecomment-5518931918
Thanks for reopening this, @jroachgolf84 — I'd like to pick it up. Before writing anything, here's the outline I'm planning to add to `debug.rst`, since the exact scope wasn't pinned down in the issue: New sections after the existing "Debugging Dags on the command line" section: 1. **Inspecting XComs during a DAG run** — pulling a task's XCom values for a specific run from the Grid view's XCom tab and via the CLI, with a pointer to the dedicated :doc:`XComs <xcoms>` page for the underlying concept. 2. **Re-running a single task from the UI** — clearing a task instance from the Grid view to re-trigger it in place, and when to reach for "Clear" vs "Mark as failed/success". 3. **Testing a single task from the CLI** — `airflow tasks test <dag_id> <task_id> <logical_date>` as a lighter-weight, single-task alternative to `dag.test()` when iterating on just one task. I'm keeping this scoped to what's directly actionable on this page rather than duplicating the dedicated XComs/UI docs. Let me know if this matches what you had in mind, or if there's a different technique you'd rather see prioritized, and I'll get started. -- 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]
