This street was also not mentioned in my notification mail as an updated street
( The reason I discovered this missed update is that in a ”competing street hunting application” I was suddenly not at 100% for Solna anymore)
This is probably the same thing that I mentioned in Mismatch nested and parent city, then I thought it was somehow connected to parent/nested cities, but this one, Solna kommun, is not nested, so there seems to be something else involved
I suspect it was just a data lag between OSM & the Overpass service I use. Edits in OSM are not immediately available via Overpass - it can lag by various amounts of time. Right now it’s serving up data from 2023-09-02T20:19:00Z
I checked the Overpass query to see what it’s returning now & I see that section of Ways is included in the response. I queued up a sync for the city, so that should fix it up. It’s just going to take a while, because I’m currently running code to add the length to each street record.
Ah, the code that handles Overpass failures wasn’t resilient enough. I’m updating it so it will clear out that date as the last step, if it wasn’t successful. This will place it in the front of the queue for the next update attempt, so hopefully won’t be too confusing to people if they happen to see it change to blank.
(Note to self: see you back here in like a month when you’ve received too many emails and need to change this behavior again)
Hm, I’ve now received some more notifications, but not all, seens to be a very long lag between update finished and notification sent. And the one that was spinning is now ok, maybe the update takes a lot longer time than I thought
It’s tough to say for certain … Some take less than a minute, some take hours.
If an update runs and nothing is changed, then no notification is sent.
Let’s see how the next update goes…
Update: Merged this into the other thread on the same topic. I’m able to see that the Cambridge update started … the Overpass server that responded had old data … and it properly re-queued the city … but the next time around, with the same issue, it did not properly reset its sync date and I can’t see how/why that could happen