-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BICYCLE transfer requests cause OTP to shut down with an error #6210
Comments
We can take a look at this next week 👀 |
I closed this because revert PR #6214 was merged. |
flaktack
added a commit
to realCity/OpenTripPlanner
that referenced
this issue
Nov 4, 2024
flaktack
added a commit
to realCity/OpenTripPlanner
that referenced
this issue
Nov 4, 2024
flaktack
added a commit
to realCity/OpenTripPlanner
that referenced
this issue
Nov 5, 2024
flaktack
added a commit
to realCity/OpenTripPlanner
that referenced
this issue
Nov 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was working on transfer request filtering and something that worked previously started causing OTP to stop from an error. I suspect PR #6179 might have broken something, because this still worked recently.
Edit: I forgot to build between checking out dev-2.x and I now edited in the proper error with the correct branch built
Expected behavior
OTP should start when the
BICYCLE
mode is included intransferCacheRequests
.Observed behavior
An error causes dev-2.x OTP to stop when trying to pre-calculate transfer requests for the
BICYCLE
mode. When I remove theBICYCLE
mode transfer requests from the config OTP starts.Error:
Version of OTP used (exact commit hash or JAR name)
commit 53a2132
Data sets in use (links to GTFS and OSM PBF files)
HSL data for most of Finland.
Command line used to start OTP
graph build
OTP start
Router config and graph build config JSON
build-config.json
router-config.json
Steps to reproduce the problem
BICYCLE
mode intransferCacheRequests
.The text was updated successfully, but these errors were encountered: