MatrixManAtYrService opened a new issue #15708:
URL: https://github.com/apache/airflow/issues/15708
**Apache Airflow version**
13faa6912f7cd927737a1dc15630d3bbaf2f5d4d
**Environment**
- **Configuration**: Local Executor
- **OS** (e.g. from /etc/os-release): Mac OS 11.3
- **Kernel** (e.g. `uname -a`): Darwin Kernel Version 20.4.0
- **Install tools**: `pip install -e .`
**The DAG**
```python
@task
def one():
return 1
@task_group
def trivial_group(inval):
@task
def add_one(i):
return i + 1
outval = add_one(inval)
return outval
@task
def print_it(inval):
print(inval)
@dag(schedule_interval=None, start_date=days_ago(1), default_args={"owner":
"airflow"})
def wrap():
x = one()
y = trivial_group(x)
z = print_it(y)
wrap_dag = wrap()
```
**What happened**:
`print_it` had no predecessors and received a
`<airflow.utils.task_group.TaskGroup object at 0x128921940>`
**What you expected to happen**:
`print_it` comes after trivial_group.add_one and receives `2`
The caller ends up with the task group itself, equivalent in the traditional
api to `tg_ref` in:
```
with TaskGroup("trivial_group") tg_ref:
pass
````
This interrupts the ability to continue using the Task Flow api because
passing it into a function annotated with `@task` fails to register the
dependency with whatever magic gets it out of xcom and adds edges to the dag.
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
