Hi, I just updated to dagster 1.0.6 (from 0.14.20), I'm getting a strange error when a run is triggered by a sensor using dagster-k8s:

TypeError: unhashable type: 'set'

Stack Trace:
  File "/usr/local/lib/python3.9/site-packages/dagster/_cli/api.py", line 395, in _execute_step_command_body
    execution_plan = create_execution_plan(
,  File "/usr/local/lib/python3.9/site-packages/dagster/_core/execution/api.py", line 989, in create_execution_plan
    pipeline_def = pipeline.get_definition()

If i look at the k8s pod log here is the full error:

Traceback (most recent call last): File "/usr/local/bin/dagster", line 8, in <module> sys.exit(main()) File "/usr/local/lib/python3.9/site-packages/dagster/_cli/__init__.py", line 48, in main cli(auto_envvar_prefix=ENV_PREFIX) # pylint:disable=E1123 File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1657, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1657, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/dagster/_cli/api.py", line 333, in execute_step_command for event in _execute_step_command_body( File "/usr/local/lib/python3.9/site-packages/dagster/_cli/api.py", line 395, in _execute_step_command_body execution_plan = create_execution_plan( File "/usr/local/lib/python3.9/site-packages/dagster/_core/execution/api.py", line 989, in create_execution_plan pipeline_def = pipeline.get_definition() TypeError: unhashable type: 'set'

Both my user deployment and the cluster are at 1.0.6. The strange thing is that if i "re-execute" the run from launchpad it works fine!

hi @Alessandro Marrella this is a known bug and there is a fix for it included in this week's release

Yay thanks! 🙏 Great to hear 😄