The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

When you use pandas pipe to stack ops on a data frame, e.g:
```def pipe_op(df):
  return df.pipe(op1)```
When this is called in a graph:
```def graph1():
  return pipe_op```
There is no reference to op1, only pipe_op.

Expected?

expected. Dagster does some magic within the body of a graph to construct the DAG - calling ops within other ops does not engage said magic.

in general, calling ops within other ops is considered bad practice bc dagster does not track those invocations as dependencies