GBFS: Correctly handle errors during provider updates #775
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Errors that occur when updating a provider (connection errors or invalid responses) are now correctly handled, reported and don't cause other providers to disappear. The existing provider data is kept and will continue to be used for routing when an error occurs during the update.
Previously, errors were only handled correctly during the initial processing of a provider.
Note: If a provider is unreachable or doesn't return a valid discovery file during MOTIS startup, it won't be available even if it becomes reachable later on (until MOTIS is restarted).
This should hopefully fix public-transport/transitous#988