-
Notifications
You must be signed in to change notification settings - Fork 34
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
Code error while retrieving trips from the server #713
Comments
The related code is here:
So line 442 is essentially a check to see if the variable is defined. So why are we getting the error? |
Logged in as this user using the emulator; no error. |
Tracing back the nextTripgj..., we find a potential mismatch - nextTrip vs. nextTripgj
But again:
|
Ok, so the answer for (2) is that the version on the staging channel (which was a backport) has matching variables. |
The answer for (3) is that |
Labeling the trip from Sun 27th at around 8am with fake labels (Pilot e-bike, Transit transfer and Walk).
So we don't have to resort to the fallback. |
Ok, so we only call the fallback when the labels were generated on a draft trip and the end of the draft trip was greater than 15 mins after the end of the real trip. I have only been labeling cleaned trips which may be why I have not encountered this before. Note also that this only happens when we try to match up the user input after the trip has processed. So the sequence needs to be:
|
If that is the case, we should be able to test this by adding a new user input with those characteristics for an existing cleaned trip. Let's do this on one of the test accounts to avoid messing up the real staging server. |
Created fake new labels that have the same start but a vastly truncated end compared to the real trip. Loaded them using
Now at
Aha! Reproduced! |
Regression caused by e-mission/e-mission-phone@3ec5734 Double-checked the commit to see if there were actually any other misses; there were not. |
Checked all instances of tripgj in this file and ensured that we hadn't broken anything else
|
As part of e-mission@3ec5734 we changed the input from a trip geojson to a trip object. But we forgot to change one of the code paths, which caused a regression. Fixed by changing the variable and the format of the variable. Testing done: - loaded fake manual entries for a test user - before the change, got the error - after the change, did not get the error This fixes e-mission/e-mission-docs#713
The text was updated successfully, but these errors were encountered: