You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when you download a client build it seems that it is trying to download it as a gzip but when you try to extract, it has some weird responses. On my system if you click on it after downloading via chrome, it appears to download it again with the same name. If you try and extract via the command line, it yells and says that it is not a gzip, and if you try and open it with something like less or a text editor it appears that the file is corrupted at the end.
After downloading the file with the same address via wget it appears that it is a proper gzip, and extracting it seems to work fine, so I think this is an issue with how we are trying to get it through our site
The text was updated successfully, but these errors were encountered:
I think this was a bug on my end. I wasn't closing the stream I was writing to and so it would be left open and have garbage in it. Having said that, since I'm attaching headers which let the browser know that the file is a gzip it will be automatically decompressed when received by users. So renaming the file before it arrives might be a good idea? I don't know how that would work exactly.
Currently when you download a client build it seems that it is trying to download it as a gzip but when you try to extract, it has some weird responses. On my system if you click on it after downloading via chrome, it appears to download it again with the same name. If you try and extract via the command line, it yells and says that it is not a gzip, and if you try and open it with something like
less
or a text editor it appears that the file is corrupted at the end.After downloading the file with the same address via
wget
it appears that it is a proper gzip, and extracting it seems to work fine, so I think this is an issue with how we are trying to get it through our siteThe text was updated successfully, but these errors were encountered: