This fix should solve the problems due to the fact that we do not clean the _user_buffer of mobility services anymore. Indeed, while this clear was removed, there is no other element to cancel the request once user has reached its response_dt. So I added a cancel_request method to remove user's request at this moment. In this way, the service stops to try to match with this user. Moreover, in the call method of the abstract travel decision model, we should compute the paths for new users AND legacy users, not only new users.
This fix should solve the problems due to the fact that we do not clean the _user_buffer of mobility services anymore. Indeed, while this clear was removed, there is no other element to cancel the request once user has reached its response_dt. So I added a cancel_request method to remove user's request at this moment. In this way, the service stops to try to match with this user. Moreover, in the call method of the abstract travel decision model, we should compute the paths for new users AND legacy users, not only new users.