Description
Description
If for some reason paket.exe is not completely downloaded during the bootstrap process (for instance , power outage), the file can be corrupted. We observed on a build server that all subsequent calls to the bootstrapper will pull an invalid paket.exe from the cache breaking builds (as in avoiding them from continuing). Cleaning paket's cache is required to continue.
Repro steps
Not sure, but creating and invalid paket.exe and placing it in cache might be enough to exemplify this. Might be able to automate it in a test.
Expected behavior
Bootstrapper should verify that the downloaded paket .exe (wether from the web or cache) is valid, possibly by comparing ti with some checksum. If the paket.exe that is present is determined to be invalid, redownload it and overwrite existing versions.
Actual behavior
A broken paket.exe is put in the .paket directory.
Known workarounds
Manually cleaning the cache will allow for a new download. This step may be limiting due to user access rights to build servers.