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

dagster

Missing something obvious here I’m sure: I have a graph definition from which I produce a job with `to_job()`. The graph has one op in it which is async and must be awaited therefore the graph function must be async as well obviously but this arrangement throws
```dagster._core.errors.DagsterInvalidDefinitionError: @graph 'nba_trends_graph' returned problematic value of type &lt;class 'coroutine'&gt;. Expected return value from invoked solid or dict mapping output name to return values from invoked solids```

Hey Ben - we actually do not yet support ops that are async functions yet. Here's where we're tracking adding support for it: <https://github.com/dagster-io/dagster/issues/4041>

ah ok - I was going off: <https://docs.dagster.io/_apidocs/ops>

I got it to run in any case by “wrapping” the async function in an dummy op using `asyncio.run()` but it’s all a bit janky

(I don’t want to use DynamicOuts/fan out as this op maintains a little cache of results just for each run to avoid unnecessary calls)