Closed fpurcell closed 1 year ago
p.s., the old call app is not having the same issue ... Barb who uses the fieldtrip app daily is saving trips off all the time with the old Leaflet version of the app. The play code is the same in production I'm trying to run here in call-test afaik -- that said, the play app in production has been running continuously w/out a restart since 2022 (so maybe we're not running the same exact code, although that said there are few changes since 2019 -- with this error popping up, I'm reluctant to restart production to find out); and the production call database has not been refreshed or reloaded for a long time either...
Hi there -- sorry about the confusion. The patch that most recently went through is not a backwards-compatible patch. This new version of the datastore is only compatible with the most recent OTP2 version of the OTP-RR front end, which uses different types
closing ... the fix will be in OTP-UI for making sure trip id is not a null field, and thus causing the NPE error described above.
running the play app in test, against a postgres database, I'm getting an error when I save attempt to save a trip:
I've dropped the database, reloaded the db with a snapshot from production, etc...
This is the exception:
FWIW, I'm using OpenJDK 8:
version of play is 1.2.5: