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

   ## Description
   
   Adds a "Debugging Dags in a deployed environment" section to 
`airflow-core/docs/core-concepts/debug.rst`, which so far only covered local 
debugging with `dag.test()` and `pdb`.
   
   The new section documents the day-to-day techniques used against a real 
deployment:
   
   - inspecting a task instance from the **Grid** view (**Logs** / **XComs** 
tabs) and via `airflow tasks state`, `airflow tasks failed-deps` and `airflow 
tasks render`
   - re-running a single task with `airflow tasks test` (no dependencies, no DB 
state) or by clearing it with `airflow tasks clear --task-regex ... 
[--downstream]`
   
   Command names and arguments were taken from 
`airflow-core/src/airflow/cli/cli_config.py` (`tasks` command group); 
`:doc:`xcoms`` points to the existing sibling page 
`airflow-core/docs/core-concepts/xcoms.rst`.
   
   closes: #71948
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (Claude Code)
   
   Generated-by: Claude Code 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).


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