ProfessionalWiki / ProfessionalWiki/Maps
`$egMapsGeoJsonCacheTtl` seems to have no effect
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 78
- Forks
- 65
- Avg merge
- 9h 17m
- Merged PRs (30d)
- 6
Description
Setup
- Maps version: 10.0.0
- MW version: 1.35.5
- PHP version: 7.4.32
- SMW version (if applicable):
Issue
I have set this var for 100 days (I assume it takes seconds)
$egMapsGeoJsonCacheTtl = 8640000;
But when I monitor the entries created in objectcache, they all get created with an expiration time of < 1 day:
> SELECT keyname, exptime FROM objectcache ORDER BY keyname;
| xpw_dev:Maps\DataAccess\CachingGeocoder: | 2023-01-22 17:37:54 |
| xpw_dev:Maps\DataAccess\CachingGeocoder:Aldi_Leipzig_Hbf_ | 2023-01-22 17:39:45 |
| xpw_dev:Maps\DataAccess\CachingGeocoder:Alnatura_Leipzig_Hbf_ | 2023-01-22 17:39:46 |
| xpw_dev:Maps\DataAccess\CachingGeocoder:Bahnhofsplatz_1_Nürnberg_ | 2023-01-22 17:38:18 |
| xpw_dev:Maps\DataAccess\CachingGeocoder:Lidl_Essen_Hauptbahnhof_ | 2023-01-22 17:37:54 |
| xpw_dev:Maps\DataAccess\CachingGeocoder:Lidl_Nürnberg_Bahnhofsplatz_ | 2023-01-22 17:38:18 |
| xpw_dev:Maps\DataAccess\CachingGeocoder:REWE_Frankfurt_Flughafen_ | 2023-01-22 17:38:50 |
| xpw_dev:Maps\DataAccess\CachingGeocoder:Rewe_Willy-Brandt-Platz_4_ | 2023-01-22 17:39:46 |
| xpw_dev:Maps\DataAccess\CachingGeocoder:SPAR_Express_Lieferservice_Frankfurt_ | 2023-01-22 17:38:51 |
| xpw_dev:Maps\DataAccess\CachingGeocoder:dm_Essen_Hauptbahnhof_ | 2023-01-22 17:37:54 |
I'd expect exptime to be somewhen end of April (100 days from now). Did I miss sth?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing where $egMapsGeoJsonCacheTtl is read and how the Maps cache entries are written to objectcache. Verify whether the configured value reaches the cache expiry calculation; done means a 100-day setting produces objectcache expiration times about 100 days ahead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100