-
-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VCS timeout is hard-coded and may be too short #2117
Comments
I tested |
Ahoj, I still have such a thing when doing I request re-opening of this issue. My internet connection, when the bandwidth is utilised, often has ping round trip times of some seconds, but the packages arrive reliably. I therefore feature request that all timeouts can be user-configured. For reasons that download fails because of upstream no longer existend, from protocol (like Here my output of
Regards! |
Affected Version
yay v12.0.4 - libalpm v13.0.2
Describe the bug
I have 14 VSC packages (and some of them are with submodules), and 20 seconds timeout is just not enough for me.
It doesn't seem to be a parallel execution, and for every devel check I get 5–7 fails (different packages each time).
I need to run
yay --devel
multiple times until all packages are updated.Reproduction Steps
yay --devel
Expected behavior
I expect the global devel timeout to be flexible rather than hard-coded.
Possible solutions:
Output
Related issue
The text was updated successfully, but these errors were encountered: