Closed leejlFG closed 3 months ago
Also TypeError: ForwardRef._evaluate() missing 1 required keyword-only argument: 'recursive_guard' when creating a new asset
Hi @leejlFG, thanks for reporting this. While we investigate, I would recommend installing an older version of grpc:
pip install --upgrade 'grpcio<1.65'
appears to solve this on my computer.
PS this also appears to break schedules:
TypeError: ForwardRef._evaluate() missing 1 required keyword-only argument: 'recursive_guard'
File "/app/.venv/lib/python3.12/site-packages/dagster/_grpc/impl.py", line 533, in get_external_execution_plan_snapshot
create_execution_plan(
File "/app/.venv/lib/python3.12/site-packages/dagster/_core/execution/api.py", line 719, in create_execution_plan
return ExecutionPlan.build(
^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.12/site-packages/dagster/_core/execution/plan/plan.py", line 1067, in build
).build()
^^^^^^^
File "/app/.venv/lib/python3.12/site-packages/dagster/_core/execution/plan/plan.py", line 182, in build
self._build_from_sorted_nodes(
File "/app/.venv/lib/python3.12/site-packages/dagster/_core/execution/plan/plan.py", line 307, in _build_from_sorted_nodes
StepInput(
File "/app/.venv/lib/python3.12/site-packages/dagster/_record/__init__.py", line 331, in __call__
self._build_checked_new_str(),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.12/site-packages/dagster/_record/__init__.py", line 342, in _build_checked_new_str
call_str = build_check_call_str(
^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.12/site-packages/dagster/_check/builder.py", line 219, in build_check_call_str
inst_type = _coerce_type(ttype, eval_ctx)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.12/site-packages/dagster/_check/builder.py", line 131, in _coerce_type
return eval_ctx.eval_forward_ref(ForwardRef(ttype))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.12/site-packages/dagster/_check/builder.py", line 99, in eval_forward_ref
return ref._evaluate(self.get_merged_ns(), {}, frozenset()) # noqa
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@cbini @tenhaus that issue is separate from this grpcio@1.65
problem
https://github.com/dagster-io/dagster/issues/22985
@cbini @tenhaus that issue is separate from this
grpcio@1.65
problem #22985
You're right. Was about the comment but got distracted by a dagster account executive adding me on LinkedIn. SHARKS! lol
This looks to be root caused by a grpcio-specific bug in v1.65: https://github.com/grpc/grpc/issues/37178
As a result, they have yanked their release of v1.65: https://pypi.org/project/grpcio/1.65.0/
Could it be that this error: TypeError: ForwardRef._evaluate() missing 1 required keyword-only argument: 'recursive_guard' is an incompatibility between python 3.12.4 and pydantic v1 (taken from here: https://github.com/langchain-ai/langgraph/issues/639). For example, I downgraded to python 3.12.3 and everything works. I also had grpcio 1.64.1.
@LaurentiuStancioiu that ForwardRef error is being tracked here: https://github.com/dagster-io/dagster/issues/22985 We have a fix going out in the next dagster release.
@gibsondan My bad haven't seen the reference which was just above! Thank you!
This looks to be root caused by a grpcio-specific bug in v1.65: grpc/grpc#37178
As a result, they have yanked their release of v1.65: https://pypi.org/project/grpcio/1.65.0/
Upgrading to grpcio 1.65.4 has removed the excessive logging for me. Other people in that thread above have said the same so that seems like a good solution for now.
Thanks for the headsup, I can reproduce that as well - we'll go ahead and remove the pin now: https://github.com/dagster-io/dagster/pull/23645
Dagster version
1.7.12
What's the issue?
Latest grpcio release 1.65.0 breaks
dagster dev
command.What did you expect to happen?
To have things spin up normally.
How to reproduce?
Upgrade grpcio to version 1.65.0 and watch the errors pile up.
Deployment type
Local
Deployment details
No response
Additional information
These errors just flow freely in the terminal until closing it, interspersed with:
until force exiting the terminal.
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.