Connection timeout too long

[opusforlife2]

What You Are Seeing?

The remote server (chocolatey.org) response request times out, after a very, very long time.

What is Expected?

Choco should have a much shorter timeout (something like 10 seconds, maybe?) and then try again (since it's a very temporary problem), and fail only after trying a few times.

How Did You Get This To Happen? (Steps to Reproduce)

This bug happens irregularly, depending on network conditions (which could be anything between chocolatey.org, the ISP, and the computer).

1. When using ChocolateyGUI, I try to update a package.
2. The update process starts, and choco.exe is invoked.
3. Then it tries to fetch the package details from chocolatey.org.
4. If there is a minor hiccup in the network that causes the response to not reach choco for whatever reason, it keeps waiting for a response, when it could just request it again (and it would work).

Output Log

I'll include the logs the next time it happens.

Full Log Output

PLACE LOG CONTENT HERE - WE NEED _ALL_ DETAILED OUTPUT BASED ON THE ABOVE TO BE ABLE TO PROVIDE SUPPORT (YOU WILL FIND THAT IN THE $env:ChocolateyInstall\logs\chocolatey.log between the `=====`)

[opusforlife2]

Oops, I forgot to mention: how do I know the timeout should be a few seconds long instead of several minutes?

When I encounter this problem, if I turn off my internet, choco detects it and returns an error message immediately, then exits. If I then turn on my internet and update the package from ChocolateyGUI again (which takes only a few seconds), the process succeeds.

[opusforlife2]

This problem is apparently more nuanced. There are instances where even turning off the internet doesn't make ChocoGUI error out and stop. The process goes on indefinitely until manually killed from the Task Manager (or at least long enough for my patience to run out).

As a mitigation, please allow the update process to be cancelled when it is not in a critical (irreversible) stage. For me, the GUI only gets stuck when the remote server is inaccessible due to temporary internet glitches, so being able to do something about the fact, rather than being stuck staring at the screen, would be awesome.

[corbob]

@opusforlife2 can you confirm that this does not happen with choco.exe? Based on the description this sounds like a Chocolatey GUI issue, and I'd like to confirm this before moving the issue to that repository.

[opusforlife2]

... I just noticed that this issue is in the choco repo and not the GUI repo. I don't remember what I was thinking when I decided to choose this repo.

Anyway, next time I have packages to upgrade, I'll try choco.exe. 👍

[AdmiringWorm]

Since this is a Chocolatey GUI issue, I'll move this issue over to the correct repository.