You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In production, after a lot of hours, it seems that the recursive function that handles VehiclePositions generation just stops. No apparent reason for it. This causes problems with Interchange.
I'm assuming Node.js is preventing infinite loops (which is technically what this is) and/or the setTimeout isn't firing sometimes.
The request listener for the VehiclePositions feed should trigger generation if the latest feed hasn't been updated in 15+ seconds.
The text was updated successfully, but these errors were encountered:
Update: it triggers a re-launch of the recursive generator function if it's been over 20 seconds since the last update.
In practice, it's updated every 10 seconds where the generator runs, waits 10 seconds, then fires again. A simple loop would cause collisions with some generation taking longer than others.
20 seconds is a reasonable-enough time to assume that the generator timed out while still short enough to not have a significant impact on realtime performance.
In production, after a lot of hours, it seems that the recursive function that handles VehiclePositions generation just stops. No apparent reason for it. This causes problems with Interchange.
I'm assuming Node.js is preventing infinite loops (which is technically what this is) and/or the setTimeout isn't firing sometimes.
The request listener for the VehiclePositions feed should trigger generation if the latest feed hasn't been updated in 15+ seconds.
The text was updated successfully, but these errors were encountered: