DagsterInvalidDefinitionError: "context" is not a valid name in Dagster. It conflicts with a Dagster or python reserved keyword #22576
Unanswered
valerio-bud
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In dagster (my current version is 1.7.10) I am getting this error when I define an asset that has both an input from another asset and wants to use the asset execution context:
dagster._core.errors.DagsterInvalidDefinitionError: "context" is not a valid name in Dagster. It conflicts with a Dagster or python reserved keyword.
This is the code:
Note that: if I remove the
context
argument frommy_asset
arguments. Then the code works, but it's weird becauseparent_asset
DID have thecontext
argument but did not raise error. So the error is raised specifically when I am usingins
in the asset definitions and thecontext
at the same time.The full stack trace:
Beta Was this translation helpful? Give feedback.
All reactions