recurring bug with new Train API NodeJS backend

40 views
Skip to first unread message

Jake Swanson

unread,
May 21, 2021, 11:34:45 AM5/21/21
to atl-transit-developers
Just in case marta people are reading this, I don't know where else to report a recurring bug that I see rarely, that I hope is already on their radar.

Every now and then in the train API I see this 500 error and stack trace as the result. I thought it was only at late-night times at first, but I am also noticing it during the day sporadically:

(as an "I wish" aside, if this code was open source I would gladly dig in your main.js file and propose a fix for this error myself, depending on whether I could understand the several hundred lines of javascript going by)

TypeError: Cannot read property 'lastArrivalTime' of undefined at C:\NewRealTrainAPINucleas\lib\main.js:647:36 at Array.map (<anonymous>) at C:\NewRealTrainAPINucleas\lib\main.js:641:33 at Layer.handle [as handle_request] (C:\NewRealTrainAPINucleas\node_modules\express\lib\router\layer.js:95:5) at next (C:\NewRealTrainAPINucleas\node_modules\express\lib\router\route.js:137:13) at Route.dispatch (C:\NewRealTrainAPINucleas\node_modules\express\lib\router\route.js:112:3) at Layer.handle [as handle_request] (C:\NewRealTrainAPINucleas\node_modules\express\lib\router\layer.js:95:5) at C:\NewRealTrainAPINucleas\node_modules\express\lib\router\index.js:281:22 at Function.process_params (C:\NewRealTrainAPINucleas\node_modules\express\lib\router\index.js:335:12) at next (C:\NewRealTrainAPINucleas\node_modules\express\lib\router\index.js:275:10)


Jake Swanson

unread,
May 21, 2021, 2:14:37 PM5/21/21
to atl-transit-developers
update: It is a known issue, related to upgrades ✅

https://twitter.com/martarider/status/1395778869244858372
Reply all
Reply to author
Forward
0 new messages