OTR_CLEAN_AGE default not correctly handled #500
Comments
|
As a workaround, add the following line to the configuration file (/etc/default/ot-recorder):
and restart ot-recorder |
ckrey
added a commit
that referenced
this issue
Oct 2, 2024
jpmens
added a commit
that referenced
this issue
Oct 25, 2024
- FIX: OTR_CLEAN_AGE default not correctly handled (#500) - FIX: ocat --dump will not output keys which don't have JSON data in them - FIX: lowercase waypoints (otrw) and config (otrc) directory and filenames (#486) - UPD: remove support for Greenwich devices (#484) - FIX: avoid a JSON object copy - FIX: print currently desired lmdb size in error that cache cannot be opened (#480) - NEW: startup message hints at configured revgeo setting and reverse geocoder brand - FIX: debian postinst now restarts ot-recorder (#446)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature introduced with #447 in version 0.9.8
If OTR_CLEAN_AGE is not specified (default = 0) or explicitly set to zero, the cache entries are always considered out of date, which leads to unintended reverse geo queries.
The cache is effectively invalidated 😭
The text was updated successfully, but these errors were encountered: