improve RAM use in city sync code, allowing me to turn that back on
- I think there are other ways that I can still speed things up, but this is good for now
- my unreliable guesstimates put the global cadence at about 1-3 months - I’ve seen anywhere from 1600 to 3300 cities updated per day lately
temporarily exclude top 20 most populated cities from regular syncing
- the updated city sync process is a bit more data/memory intense, so I’ve got the biggest dangers excluded for now
- I want to let the sync process run for a while, so cities can get their updates
- after things are in a nice spot, I’ll pause syncing again, push through these large cities, and monitor resource usage to see how careful I really need to be
stop repositioning the map when navigating to the Route Builder page- update Garmin authentication to meet their end-of-year deadline
- there shouldn’t be any visible difference (one person noticed duplicate Garmin entries in their Settings page while I was working on the transition)
- this included a fix for an authentication issue when the Garmin Connect app is installed
add a script for myself to handles cases where Streets display the wrong node count (e.g. indicates 20 nodes on the page but shows 2 on the map) … If you notice cases where the count is wrong, let me know and I can clean it up (as far as I can see, this is an issue that was resolved some time ago)- fix a few places where pagination could produce duplicate results across pages
- fix an issue where people who just became a Supporter might have their LifeMap cleared out … it could happen if they became a Supporter while there was an unusual delay in the Supporter LifeMap rebuild queue
- fix a bug when removing a manually completed street while its city is syncing … only I saw this one, but the result was that certain jobs would hang indefinitely
- fix a bug with Route GPX downloaded file names where some browsers/devices would give a
route-name.gpx.xmlfile instead ofroute-name.gpx - fix the special Challenge pages (e.g. Nodevember) to properly show the last event’s results while the next event is upcoming within the same year
fix a few weird line height cut-off issues- fix dark mode text color on Links page
- various software updates
14 Likes
Would you mind giving us the list of the 20 paused cities? I’m in Chicago and trying to complete the city on Hard Mode, and there are some very distant neighborhoods I don’t want to finish until I confirm streets that ought to disappear in the next update actually do (previously marked as public but have private/no trespassing signs so marked on OSM as private, for example). I wouldn’t be shocked if Chicago was a top 20 Citystrider-populated city; just trying to calibrate expectations! Thanks!
@JamesChevalier bumping this - I have the same question about Chicago city sync being paused for a few months now
If there are more than 4k runners there, it’s paused. I’m working on getting rid of that limit - I have a bit more testing to do though.
I can include Chicago in my testing now - I just started its sync.
1 Like
@JamesChevalier how did the testing go? Some of us Chicago runners identified OSM issues with the latest sync which we’ve since resolved, so we’ll refresh again once CS allows us to do so
It’s going to take me a while to figure out if/how I can remove the pause limitation.
The individual Chicago sync went well, but I have several cities in this size range where it would be incredibly destructive if a few of them happened to sync at the same time.