https://prefect.io logo
Join Slack
Powered by
This message was deleted.
# ask-marvin
s
This message was deleted.
m
Your message was too long by 427 tokens - please shorten it and try again. For reference, here's your message at the allowed limit:
Hi, I am trying to deploy a flow which takes in a dictionary as a parameter. However, my flow is constantly erroring out with something like this in the prefect worker
``` 090211.855 | ERROR | prefect.engine - Engine execution of flow run '6b16ec04-2fde-480b-8491-7ccc4f4e42dc' exited with unexpected exception │ │ │ Traceback (most recent call last): │ │ │ File "/home/venvs/.venv/lib/python3.11/site-packages/prefect/engine.py", line 2917, in <module> │ │ │ enter_flow_run_engine_from_subprocess(flow_run_id) │ │ │ File "/home/venvs/.venv/lib/python3.11/site-packages/prefect/engine.py", line 318, in enter_flow_run_engine_from_subprocess │ │ │ state = from_sync.wait_for_call_in_loop_thread( │ │ │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ │ │ │ File "/home/venvs/.venv/lib/python3.11/site-packages/prefect/_internal/concurrency/api.py", line 243, in wait_for_call_in_loop_thread │ │ │ return call.result() │
Passing a dictionary as a parameter to a Prefect flow is indeed possible. The error you've encountered, however, does not seem to be directly related to the fact that you're using a dictionary as a parameter. It appears to be an internal problem with Prefect itself, possibly a bug or a misconfiguration. Given that a search for issues with the 
AttributeError
relating to 
should_validate_parameters
did not return any results, it could be a new or less commonly reported issue, or it may have been resolved in a version of Prefect that you're not using. Can you verify the version of Prefect you're using, and ensure it's up to date? If updating doesn't resolve the issue, you might consider reporting the bug through GitHub to get input directly from the Prefect developers. They might need specific details about your flow, the way you're passing the parameter, and the environment in which you're running the flow. In the meantime, you can try these steps which often help resolve issues like this: 1. Ensure your Prefect installation is up to date. 2. Confirm that your flow's usage of parameters follows Prefect's documentation, particularly how parameters are defined and passed. 3. Check for any decorators or additional logic that might be affecting the Flow object and causing the attribute error. Unfortunately, without seeing your flow definition, it's challenging to give a more precise solution. A more detailed error log or a snippet of the flow definition could provide better insight. If the problem persists, you may want to report the bug, including as much detail as possible so that it can be diagnosed by the Prefect team.
2 Views
Open in Slack
PreviousNext
Powered by