Dagster 0.9.18: @pipeline 'pipeline' has unmapped output 'result'. (my return type is `-> None`)
See original GitHub issueHi,
I’m trying to update dagster to the latest version in my pipeline and I’m getting this error because my pipeline function is annotated with -> None
as the return type.
The error disappears if I remove the return type, but that would make mypy unhappy (and #type: ignore
doesn’t work well with annotated functions).
Should the error be raised if the return type is None
? If yes is there any workaround you can suggest? I’d prefer not disabling mypy if possible.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Ops - Dagster Docs
Input and output management: Ops have defined inputs and outputs, analogous to the arguments and return value(s) of a Python function. An input...
Read more >dagster Changelog - pyup.io
Fixed a bug where the re-execute button on runs of asset jobs would incorrectly show warning icon, indicating that the pipeline code may...
Read more >View Options
Some Dagster packages have more involved test configs or support only certain Python version; ... yield Output(value=table_name, output_name="result").
Read more >Dagster with User Code Deployments (gRPC)
Dagster is an open source data orchestrator for machine learning, analytics, and ETL that makes your pipelines more reliable and robust.
Read more >How to use the dagster.check.failed function in dagster - Snyk
To help you get started, we've selected a few dagster examples, based on popular ways it is used in public projects. Secure your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
fix linked above will go out in the release today
Thanks! The speed at which you folks work is incredible!