Open nstCactus opened 2 years ago
Hi @nstCactus!
I have same issue here!
The solution for this problem will be add a little interval between requests to Gitlab. But I didn't identify the file that makes this request yet;
Same here.
I found a possible workaround: getting only the last ten releases. This is less than ideal…
When importing a new package from a private gitlab.com repository, most of the time I get an error during the package syncrhonization step that immediately follows.
When downloading this URL using my brwoser, everything works fine.
Digging in the output of the
bin/console messenger:consume -vvv
command output, I found the following error:After waiting for some time and forcing a new sync, it usually succeeds, but it's a pain having to go through this every time.
I am the only one facing this issue? Is there any setting I can change in either gitlab.com or repoman to mitigate this issue?