Closed rcavaliere closed 2 years ago
For problem 1 I created a shell script and tried to do this call 100 times in a row. I couldn't reproduce the issue. The data was always complete. Maybe it got solved on one of the previous releases or it was a temporary problem. In any case, I would suggest to add a select
request parameter to drastically reduce the payload and maybe it could also solve the issue on their side.
Same for number 2, since it is closely related to 1 I can't reproduce the issue.
For problem 3: I'm also not able to reproduce it, but I'll create a separate issue on ninja. In the meantime my suggestion is to handle the 400 status code and redo the same request if it only happens rarely.
They talk about contemporaneous calls of all echarging types... maybe that causes the problem... was not able to reproduce either. I think we need more information about the calls... that is not just the single calls, but which get called at the same time.
Well concurrent queries should not affect the results. How is that even possible?
Theoretically not, but who knows... we had concurrency problems in the past... should be fixed by now.... but just saying that we might need more information....
@bertolla @Piiit I got a feedback. The error is obtained if you make several times requests one after the other, see video...
https://user-images.githubusercontent.com/9825179/128006785-2f6cf94f-ffdf-4562-aeb5-a0e25a8bf96f.mp4
This is just one of the issues which needs to be addressed. I created a first issue here: https://github.com/noi-techpark/it.bz.opendatahub.api.mobility-ninja/issues/20
@rcavaliere I think I have pinned down this issue, it should now work and is testable on our testingmachine.eu instance.
Testable with https://mobility.api.opendatahub.testingmachine.eu as base URL...
Could you please get in contact with Projektionisten and ask if they could test again. Are they on github? So we could invite them directly to this issue?
The commit that solves this issue is https://github.com/noi-techpark/it.bz.opendatahub.api.mobility-ninja/commit/57e02f053835a5172a1165c2b55d0c7a93a3c66f
@Piiit testing by Projektionisten done, works well! Let's go in production with this bug-fix
@rcavaliere on production now, please test again with the production endpoint
UPDATE 2021-09-29
The developers of the suedtirolmobil channels (Projektionisten) are developing for STA the integration with ODH Mobility in order to see real-time information about other mobility services on the map. During the implementation, following issues have been found:
Problem 1
Problem 3
Problem 4