fix an assertion that would fire erroneously fire due to int overflow

Open woodpeck opened this issue 3 months ago • 1 comments

I have recently had osrm-contract abort on a full-planet import with v6.0.0 with the problem described in issue #5440. The modification of the assertion described in that issue solves the problem but it appears it has never made it into the code proper. So here's a PR that does that; after the modification, the osrm-contract step runs normally and produces a functioning routing graph.

Oct 10 '25 14:10 woodpeck

@woodpeck I have the same problem - would be good to merge. I see that one test fails - is it normal?

Oct 27 '25 07:10 Charmik