Good morning. On this section of the map I-69E N and S, frontage road, ramps, and LS I can’t make edits. Sometimes I’m able to change something like the Speed Limit but it locks up WME and I have to hard refresh. I’ve tried prod with scripts, prod incognito, and beta incognito and nothing I do works. I’ve tried moving nodes, cutting segments, and adding shields. None of that works. I’ve had three other senior editors try and they can’t get the segments to be edited either. Thank you.
I looked at a similar issue in that area the other day. I did finally manage to get a segment to split but required me to nudge a junction node, save, then split. When I tried to just split, I got the error saying the segment ID was not in the data model. If I try to take the segment before the on-ramp here https://waze.com/en-US/editor?env=usa&lat=26.40776&lon=-97.78454&zoomLevel=19&segments=531641679 and then attempt to add a TIO to include the shield onto the ramp, once I hit apply to the shield it throws and error:Uncaught Error: segment with id "503697744" wasn't found in dataModel
at hr.getEntrySegmentOfTurn (app-62f88338199f980e5d99.js.gz:1:983899)
at hr.drawPathEntryMarker (app-62f88338199f980e5d99.js.gz:1:983037)
at hr.drawPathEntryMarkers (app-62f88338199f980e5d99.js.gz:1:982973)
at hr.draw (app-62f88338199f980e5d99.js.gz:1:982671)
at v (third_party-45fe9aba9d649e1fe91a.js.gz:2:1169484)
at y (third_party-45fe9aba9d649e1fe91a.js.gz:2:1169276)
at d (third_party-45fe9aba9d649e1fe91a.js.gz:2:1167229)
at u.trigger (third_party-45fe9aba9d649e1fe91a.js.gz:2:1169169)
at m.putTurn (app-62f88338199f980e5d99.js.gz:1:117838)
at g.doAction (app-62f88338199f980e5d99.js.gz:1:56172)
That segment ID doesn’t appear to be on the map in that area, which suggests that something on the map may be referencing it somehow and causing it to throw an error.
What I did notice is that the Northbound and Southbound frontage leading into Broadway both have paths on them, but the icons keep disappearing. Not sure if that’s related or not.
I know that when you put a closure on a recently deleted segment through reportal it does lock up the map the same way, so it might indeed be something like that.
I’m seeing a “freeze” issue doing other tasks with similar error message in the console. I was trying to close a UR (here, on clicking save, the error below was generated:Uncaught (in promise) Error: segment with id "21148707" wasn't found in dataModel
at hr.getEntrySegmentOfTurn (app-62f88338199f980e5d99.js.gz:1:983899)
at hr.drawPathEntryMarker (app-62f88338199f980e5d99.js.gz:1:983037)
at hr.drawPathEntryMarkers (app-62f88338199f980e5d99.js.gz:1:982973)
at hr.draw (app-62f88338199f980e5d99.js.gz:1:982671)
at v (third_party-45fe9aba9d649e1fe91a.js.gz:2:1169428)
at y (third_party-45fe9aba9d649e1fe91a.js.gz:2:1169276)
at d (third_party-45fe9aba9d649e1fe91a.js.gz:2:1167229)
at u.trigger (third_party-45fe9aba9d649e1fe91a.js.gz:2:1169169)
at m.fromDescartes (app-62f88338199f980e5d99.js.gz:1:119721)
at qe._updateTurnGraphConnections (app-62f88338199f980e5d99.js.gz:1:850028)
There is a path defined here https://waze.com/en-US/editor?env=usa&lat=30.00565&lon=-90.15942&zoomLevel=18&segments=511606375. I’m making an assumption based on the code function names, but it seems to suggest that a path object exists in a table somewhere that includes a segment, and that segment was changed, but the path object was not updated with the new segment IDs, such as a split or a delete.
Thank you John for checking this. I will forward all information to the team and they will review the behaviour. These paths might really affect the process.
I think this is still a bug, and probably needs to be investigated. I’ve come across several issues where I’ve tried to save, and the UI greyed out and stopped responding. For example, I was adding a closure on the ramp here, and then close the MP.Uncaught (in promise) Error: segment with id "529223958" wasn't found in dataModel
at Ar.getEntrySegmentOfTurn (app-e5b1bb07d7fdfd545428.js.gz:1:1025954)
at Ar.drawPathEntryMarker (app-e5b1bb07d7fdfd545428.js.gz:1:1025092)
at Ar.drawPathEntryMarkers (app-e5b1bb07d7fdfd545428.js.gz:1:1025028)
at Ar.draw (app-e5b1bb07d7fdfd545428.js.gz:1:1024726)
at v (third_party-f5d5a23ec5aaa2d8fd15.js.gz:2:1178007)
at y (third_party-f5d5a23ec5aaa2d8fd15.js.gz:2:1177855)
at d (third_party-f5d5a23ec5aaa2d8fd15.js.gz:2:1175808)
at u.trigger (third_party-f5d5a23ec5aaa2d8fd15.js.gz:2:1177748)
at g.fromDescartes (app-e5b1bb07d7fdfd545428.js.gz:1:120881)
at Ye._updateTurnGraphConnections (app-e5b1bb07d7fdfd545428.js.gz:1:892670)
I get this even when trying to use the “repeat next day” feature on the closures tab. There are multiple paths in this area, such as on this segment here.
On poking around, the path segment is found just a little south from the one above, here. If I click on that segment, there is an exclamation mark that says that lanes will not be shown to the driver, and that I should click save.
As I don’t want to break the error condition, I’ve not touched the impacted segment, to allow for developers to investigate.
