termux-change-repo: promote mirror.termux.dev #46
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
I think it should be improved before promoted more, main issue is that it redirects every call to a random close mirror, so if 3 mirrors are roughly the same distance then each might be used. This is problematic since different mirrors sync at different times and with different intervals, so you might get the Packages list from mirror A, and then try to download a package in the list from mirror B which does not have it (yet). Would be better if it would select a mirror and then stick to that one for all calls from a certain IP address for, say, 5 minutes. Maybe there is a better program than mirrorbits to solve this particular problem |
a0aac3f to
a2bb0a2
Compare
Contributor
Author
|
Abandoned per termux/termux-packages#18311 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I think should give more spotlight to mirror.termux.dev which is buried deep in the list.
My testing (depending on time):
Best case: it works flawlessly
Bad case: it needs 5 or more retries to get my packages updated (package not found in mirror, redirection to http #47)
Worst case: it fails to get the metadata (incorrect size etc)