Closed jneira closed 3 years ago
From the experiments I ran, when it was failing to get through, it was taking literally forever - a longer timeout wouldn't help. The issues started occurring a week or so ago and are being tracked at https://github.com/fpco/stackage-server/issues/291. That said, if you can find a setting that reduces it or makes things work even so, happy to apply it.
Closing as i am not using azure anymore and the reasons noted above
Hi! In hie we have to generate the hoogle database in our azure ci env and it has started to throw response time outs downloading
cabal.config
from stackage nightly or lts. The issue is related with the environment, locally i've got to download all files, although they can take several seconds. In past succesful builds i see in logs:In failed ones :
when it get to downlaod nightly (in most of them the timeout is with nightly itself)
Locally i am getting just now:
but the timeout is not triggered.
Surely the root of the problem is not with hoogle itself but is there some way to increase the response timeout with some config and work around the issue?