<@ULVA73B9P> I upgraded from `2.12` to `2.14` and...
# ask-marvin
m
@Marvin I upgraded from
2.12
to
2.14
and now when I try to run an ECS task it gives me this
ValidationError: 1 validation error for ECSTask command value is not a valid list (type=type_error.list)
. Any idea how to fix that?
n
@Marvin alive?
m
Yes, I'm here! How can I assist you today?
n
@Marvin do you remember what you were asked?
m
As a chatbot, I don't have the ability to remember past interactions. However, I can retrieve information from the application's state. Currently, the state contains some records about Prefect 1 and Prefect 2. Is there something specific you would like to know?
n
@Marvin I upgraded from
2.12
to
2.14
and now when I try to run an ECS task it gives me this
ValidationError: 1 validation error for ECSTask command value is not a valid list (type=type_error.list)
. Any idea how to fix that?
fwiw i suspect a pydantic 2 error
m
I'm sorry, but I couldn't find any specific issues related to your error on GitHub. However, the error message suggests that the command value you're providing to the ECSTask is not a valid list. In Prefect, ECSTask expects the command to be a list of strings. If you're providing a single string, you might need to split it into a list. For example, if your command is
"echo hello"
, you should provide it as
["echo", "hello"]
. If you're already doing this and still encountering the error, it might be a good idea to check the Prefect documentation or ask for help in the Prefect community.
n
but if not i would have to see the trace
m
I couldn't get more of a trace, even after setting
PREFECT_LOGGING_LEVEL="DEBUG"
on the agent
I don't pass a
command
arg at the moment ftr
n
hmmm why are you not passing a command?
m
Never needed one before
n
well i think we provide a default command that invokes the engine if you dont
m
Yeah, figured that was getting handled somewhere!
trying to inject an empty list now manually
@Nate So, if I run a script manually and deploy it, it works. But when I added it to library code, re-made the image, and ran CI/CD, the flows deployed that way give me the same error
Had to manually delete the existing version. but it works now! Thanks!