New RunLLM response generated: >>>*# Question* Has anyone else noticed less clear error messages on flytekit 1.13.1 than in 1.12.0? Those just happen to be version we were trying, but here are the error messages we got with each version with the same code setup. The 1.12.0 error is much clearer and directly points out the problem, while 1.13.1 says invalid argument, but then makes it sound like its a cache issue or version issue or something 1.13.1

Request rejected by the API, due to Invalid input.
RPC Failed, with Status: StatusCode.INVALID_ARGUMENT
        details: task with different structure already exists with id resource_type:TASK project:"flytesnacks" domain:"staging" name:"path/to/function" version:"<version>"

1.12.0

FlyteAssertion: USER:AssertionError: error=Input model_version of type <class 'str'> was not specified for function <function_path>. Flyte workflow syntax is a domain-specific language (DSL) for building execution graphs which supports a subset of Python's semantics. When calling tasks, all kwargs have to be provided.

# Answer Yes, there have been reports of less clear error messages in newer versions of Flytekit. According to this GitHub issue, users have noted that error messages in Flytekit can be hard to decipher, and there is an ongoing effort to improve them by providing richer context and hints on how to address the errors. Would you like more details on the specific changes between versions 1.12.0 and 1.13.1, or guidance on how to handle these errors? Sources: - this GitHub issue Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1723828407.204219 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.