Closed satabin closed 2 years ago
The OTP1 GraphQL API is not maintained, I would recommend using the HSL fork version or maintaining your private fork until you can switch to OTP2.
Hi @t2gran thanks for the answer and suggestion.
Hey @satabin ( :) ), does this problem still happen in OTP2?
This part was completely rewritten in OTP2, so they probably don’t.
I’m closing this, I thought I did it before.
In the current graphql API, call may crash when
semanticHash
Expected behavior
The calls don't crash. The semantic hash is returned, and the scheduled timetable is used
Observed behavior
Cast or null pointer exceptions are raised.
Version of OTP used (exact commit hash or JAR name)
33a85ef9af5d1f3f028c34d1f328adb30e2cf25f
Data sets in use (links to GTFS and OSM PBF files)
N/A
Command line used to start OTP
N/A
Router config and graph build config JSON
N/A
Steps to reproduce the problem
Query a trip with its
semanticHash
orstoptimeForDate
on a data set with no updater.