vscode: 1.31.1 update has different checksums on different locations

I’ve purged the CDN cache for /stable/1b8e8302e405050205e69b59abb3559592bb9e60/code-stable-1549938209.tar.gz. The file should be OK any time soon.

I also have an open ticket with the CDN provider. Let’s see if they find the issue.

For the guys still having issues, try erasing your package manager’s cache. In my case, deleting /.cache/yay/visual-studio-code-bin and then attempting a full system upgrade yay -Syu triggered the download of the file with the correct checksum. You might have to google where your package manager’s cache folder is located.

@joaomoreno @dcelasun

Congratulations on the help of everyone involved. The problem was solved. I just tested with the yay package manager.

If you cannot wait I’ve used the process described by @xereda to download the proper file, and then moved it to where my AUR builds happen (I’m using Manjaro Linux and its Package Manager).

Since the visual-studio-code-bin folder was not destroyed after the first failed attempt we can just replace the “code_x64_1.31.1.tar.gz” file: mv code-stable-1549938209.tar.gz /tmp/pamac-build/visual-studio-code-bin/code_x64_1.31.1.tar.gz

And when trying again it skips the download process and uses the good file, passing the sha256sum test.

Checksums now match, thanks a lot! 😉

https://github.com/Microsoft/vscode/issues/68736

@xereda Can you try again? This download should be fixed by now. I’ve opened a support ticked on our CDN servers.

I did a test downloading the file through a proxy site. I opted for a European server. Now the downloaded file is not corrupted. You can analyze in the simulation illustrated below:

The .tar.gz file provided by the Vscode site is corrupted.

Note that the original file usually stands around 65mb. This file, downloaded, is 14mb.

Thanks for the confirmations!