Replies: 2 comments 1 reply
-
|
You can try setting |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I had the same problem within a bigger open wifi network. @wbthomason 's answer fixed it for me: local packer = require('packer')
packer.init {
max_jobs = 1,
}
packer.startup(
function(use)
... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have very slow and very high latency (non-Starlink satellite) internet. One thing packer really struggles with for me are installs/updates/syncs. I've increased the git timeout to 600 seconds, but that doesn't always do the trick. I find things still fail for no good reason. I can -- and often do -- manually git clone into the proper pack/packer directory and almost never have an issue with the clone. I suspect the issue might be the large number of clones being done all at the same time. I wonder if it would be possible to either turn off async clones or to add a limit to the number of queued clones.
Beta Was this translation helpful? Give feedback.
All reactions