Closed amotl closed 3 years ago
When purging the cache using
rm -r ~/Library/Caches/wetterdienst
it started working again.
Unfortunately, the location of the cache directory is not printed on startup, so the average user will have no clue what is going on. This logging command was intentionally placed here, but apparently the logger has not been configured at this time already.
Why the cache got corrupted at all is also beyond my current knowledge. It's just that it has already tripped @sk-drop the other day, see #217.
Describe the bug After installing
wetterdienst
within a fresh virtualenv directly from the Git repository and trying to acquire data using its command line interface, it croaks. This is coming from trying to reproduce the issue #230 @wetterfrosch is observing.To reproduce
Expected behavior Installing and invoking
wetterdienst
should just work (TM).Screenshots C'mon ;].
Version information OS: macOS
Additional context Maybe it's related to the dogpile cache again? See also #217.
Full traceback