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.
As discussed here and here, the default timeout for RT downloads of 10 seconds may be too short for large feeds, because it seems to encompass the entire transfer and not only until the first packet. As far as I understand, it can be increased without risking exceeding the 60 seconds interval because the downloads run in parallel. Increasing the timeout to 30 seconds has helped for Transitous.
For some reason, it does not seem to throw a timeout error, but returns some garbled protobuf out of which it even succeeds to read a very small number of trip updates. When testing locally, I do get a timeout error as expected.
Btw, I'm seeing in the logs of my DELFI RT feed mirror that some instance running at TU Darmstadt is also frequently hitting the 10s timeout. Would be interesting to know whether it also doesn't throw timeout errors.
(... and a typo fix)