In migration from 0 9 3 to 0 10 4 we re seeing a typing erro

Question

In migration from 0 9 3 to 0 10 4 we re seeing a typing error ```dagster core errors DagsterInvalidDefinitionError Invalid type dagster type must be DagsterType a python scalar or a python type that has been marked usable as a dagster type via usable dagster type or make python type usable as dagster type got typing NoReturn``` on something that was previously working Is there a dagster typed equivalent of NoReturn or should I mark NoReturn as usable

alex · Answer

can you share the code in question or an approximation If its what im thinking im surprised this used to work You likely just need to manually declare `output defs= `

Paul Wyatt · Answer

It s complaining about a pipeline definition ``` pipeline preset defs=training presets mode defs=DEFAULT MODES def message sentiment analysis cardiff train gt NoReturn Test pipeline for modularization y df = orc initialize learning task ```

Paul Wyatt · Answer

In this case the return type is mostly there as coding convention It s not particularly meaningful

alex · Answer

ahhhhh interesting

alex · Answer

I think it will work if you switch it to `None` which I believe is what it should be since `NoReturn` is for functions that never return ie always raise exceptions Python functions without an explicit `return` implicitly `return None`

alex · Answer

thanks for the report the core of the issue was an unintended consequence of some work for <https github com dagster io dagster discussions 2902>

Paul Wyatt · Answer

Thank you