Open khaeru opened 3 years ago
I'd say this is more of a bug than a workaround we need to document. If it's commonly experienced and we can't figure out the underlying bug we could probably catch the exception and clear the cache through the python api.
FYI, after 3b260104e2c513927b07a9a36724078932439d82 we should no longer be generating a new cache file for every minor version of python which should eliminate the collection seen here. That doesn't explain this error though.
Upon upgrading some Python packages (I think including dogpile.cache), I began to see:
After poking around at the code for a while, I found and deleted the following files in ~/.cache:
The errors disappeared and
bugwarrior-pull
worked again.The name of these files is non-obvious; I was looking for ~/.cache/bugwarrior or similar. It would be nice if the documentation included a description of this location, so that users could have some hope of finding and clearing the files to overcome such problems.