New RunLLM response generated: >>>*# Question* Hello all We have been working with flyte for some type and have been looking into setting the cache_version for tasks automatically. Depending on a change in any of the python files that go into a task then the cache_version is changed We have solved it ourselves by extending the decorator and it's working. My question, is this a usecase that you could see flyte supporting in the long term/have planned? # Answer Flyte currently requires users to specify the

cache_version

manually for tasks, which can be error-prone. There is an open issue discussing the possibility of automatically deducing the

cache_version

for certain task types, such as SQL queries or Sagemaker built-in algorithm tasks (GitHub Issue #770). This indicates that the Flyte community is aware of the need for such a feature and is considering it. Would you like more details on the current discussions or potential workarounds? Sources: - GitHub Issue #770 Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1725371912.596919 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.