https://prefect.io logo
Title
e

emre

08/29/2019, 11:34 AM
Hello everyone, I started getting a warning for each task in any of my flows, logging: “can’t use cache because it is now invalid” The odd thing is that I am not using caches at all. This warning should be triggered
if task.cache_for is not None
according to the
task_runner.py
source code. I double checked that all my tasks have a
cache_for
value of
None
. I’ve been away from Prefect for about a month and don’t remember getting this warning at all, And I haven’t changed versions. Has anyone experienced a similar issue?
j

Jeremiah

08/29/2019, 12:31 PM
Hey Emre, that message was a bug accidentally introduced in 0.6.0! It's been fixed in 0.6.1. Fortunately it's just a message, not affecting functionality.
Although if you haven't changed versions that's interesting 🤔
I believe that message (and related bug) are only in 0.6.0
e

emre

08/29/2019, 12:56 PM
Yeah turns out i did change 😅. Forgot that I was working on a new project with a fresh virtualenv. I’ll upgrade right away.
j

Jeremiah

08/29/2019, 12:57 PM
Ah good ok! Sorry for the inconvenience.
e

emre

08/29/2019, 1:00 PM
No worries, its my bad anyways.