Why is it a problem since you get credit for a street without much effort?
You may believe that you have completed a neighborhood but sooner or later, the bug will be fixed, and you may have to come back for just one street or two. And even if you are aware of the bug, the red nodes are not showed anymore with the node hunter, and it makes striding more difficult, especially in large cities.
I suspect that this bug happens because the completion is not re-checked when new nodes appear (thus changing the percentage of completion). I donāt know whether @JamesChevalierās corrections from the last days already deal with those situations. I hope so, and in this case, there is no to do, but after running almost 20 streets today that were wrongly marked as complete before my run (mix of the this bu and https://community.citystrides.com/t/user-setting-hard-mode/17458/12, I decided to make my finding official.
Paris was updated today (2021/02/25). I still have 2 ācompleteā streets there with respectively 25% and 50% of the nodes complete. These 2 streets should be incomplete, what they are not.
My interpretation is that the issue has not been solved by the multiple updates in the last weeks, and even if most striders do not invest any time to check this kind of things, it is a serious bug.
Yeah it looks like nodes are being added to streets, and anyone who has already completed the streets is left as complete.
This is something that Iāll have to look at separately from any of the other city update issues (which I think Iāve resolved). Thanks for reporting this!
I have something that will address this going out in the next release.
Thereās new code at the point of adding new nodes to existing streets. It kicks off a new set of jobs that will check whether the street is still completed (for anyone who has already completed it) & if itās not then itāll unmark it. If it happens out that youāve already completed the node that was added, the existing system will pick that up & re-mark the street as completed.
It wonāt address existing streets that are improperly marked as complete - Iāll need to manually start that for people (unless I happen to think of a safe way to look through everyoneās data).
Iāll post again here after itās out & Iāve reprocessed your accounts.
Today I noticed a similar thing.
A street was marked as completed after my run today while I have not run a section.
However the part I completed today probably contained a lot of nodes. So maybe Iām above the 90% that Denis mentioned.
The thing is that if I show the street, you still see red nodes.
However I can only find the street in ācompletedā streets, not in āincomplete streetsā.
I would prefer a street is only marked as complete if all nodes were tackled. Or is that not the way it works?
The default āruleā is completing 90% of a streetās nodes will mark that street as complete. If you want to operate on a 100% āruleā then it sounds like you want to enable hard mode: User Setting: Hard Mode
In some rare cases, the issue remains. This street is marked as completed in the nested city after multiple updates while I only have 89% (and hard mode enabled). It is marked as incomplete in the parent city.
My current guess is that the street is previously completed ā¦ a city update runs that adds nodes to the street ā¦ and my code does not look to see if any streets should be un-marked as complete. Iāll put that on my to-do list.
I searched around for Grenzweg (sharing links makes debugging much much easier for me) and found that it had 23 new nodes created in the March update. That seems to fall in line with my guess.
Manually running the street validation code correctly un-marked it as complete, so I queued up that job for all your streets.
Hi @JamesChevalier , Hereās another effect of that same issue, I think.
The street shows as incomplete in my city view but it doesnāt affect my 100% completion of the city.
Itās amusing to see Iām in second place now for the city while it shows I have 100%. Kransackerweg - CityStrides
To solve it I think I could mark and unmark complete manually. But I didnāt, just to show you this.
Thanks James.
For 10 says, nothing happened, but last night, I lost 100% completion in 6 proper cities and 1 nested city within a few hours. 2 more nested cities will follow since there are now new nodes in the parent city.
Some were normal updates but in most cases, the now incomplete streets were not updated so I guess it has to do with the re-processing.
I have already caught 4 streets today and I have planned 6 new runs with the route builder to get the rest until the end of June.
Did you previously have this street in your completed list?
Iām trying to figure out if it was previously complete & updated to make it incomplete (e.g. more nodes added that you havenāt run by) ā¦ or if itās a new street that went directly to your incomplete list (this looks like it is the case, but Iād like to be certain).
At first I thought that nodes where added, because Iāve already ran part of this street.
But indeed, it turns out this is a newly added street.
Latest CS city update of the fifth of May.
Alright, Iāve got code in there now that will recalculate city progress when adding new streets ā¦ then recalculate progress again after the new nodes are added & processed. So during the city update, percentages may fluctuate. Iām really hoping that this isnāt noticeable since the updates are running pretty fast now.
@dbafounta Iām unsure if youāre reporting further issues with streets being marked as incomplete even though they are complete ā¦ or if youāre just noting that the updates are adding to areas where you havenāt run yet.
two posts up - this is being taken Very Seriouslyā¢ and is of High Importanceā¢ and We Have Our Best Minds On Itā¢ (wellā¦) 
