Expected behavior

When paging over routing results we should not get duplicates. Realtime updates may cause duplicates, and that is hard to avoid, but realtime is not involved in this issue.

Observed behavior

The last itinerary in the first search is present in the next page:

Query

The "numTripPatterns": 2 is set just to restrict the number of itineraries, but unsetting it or setting it to another value still produce the same bug.

Version of OTP used (exact commit hash or JAR name)

latest

Data sets in use (links to GTFS and OSM PBF files)

Norway

Steps to reproduce the problem