Andrey Anshin

TaskGroup it is a UI / Namespace feature, and do not have own states, like a DAG or TaskInstance have, that mean without [significant changes](https://cwiki.apache.org/confluence/plugins/servlet/mobile#content/view/89066602) in Airflow codebase it is...

I'm not sure this one fix link to the sources. Because these directory not included into the build this kind of sources in `apache-airflow` documentation. I could have a look...

@RNHTTR After minor changes in doc configurations `tests/system/core`available into the `apache-airflow` documentation https://github.com/apache/airflow/assets/3998685/446a03a6-3f39-4d72-a423-b078998cc0f3

Tests my changes (most of them just cosmetic), look good

> if there is a better way to do this without changing the code Better way contribute this changes to Airflow codebase. I do not sure that you could provide...

> If "Other Airflow 2 version" selected, which one? > 2.7.3 Is it reproduced in latest Airflow (2.9.0 at that moment)?

Checked my changes, all looking good

Is it reproduced in the latest [`apache-airflow-providers-elasticsearch`](https://airflow.apache.org/docs/apache-airflow-providers-elasticsearch/stable/index.html)? And maybe also worthwhile to check on the latest Airflow ([2.9.0](https://airflow.apache.org/docs/apache-airflow/stable/release_notes.html) at that moment)

Seems like this one a duplicate of https://github.com/apache/airflow/issues/33692

I guess the better solution would be disable extra debug ranges by set implicitly [`PYTHONNODEBUGRANGES`](https://docs.python.org/3/using/cmdline.html#envvar-PYTHONNODEBUGRANGES) to any value with ability to set it off Without this feature traceback seems like...