Closed Shades-McGee closed 3 years ago
In the meantime I've confirmed that this zip is only corrupted in the version that's still in the ATS cache, if you bypass the ATS cache you get a zip that passes integrity checks:
$ curl https://spacedock.info/content/Nertea_200/Near_Future_Spacecraft/Near_Future_Spacecraft-1.4.1.zip -o Near_Future_Spacecraft-1.4.1.cached.zip
$ curl https://spacedock.info/content/Nertea_200/Near_Future_Spacecraft/Near_Future_Spacecraft-1.4.1.zip?uncached=$(date +%s) -o Near_Future_Spacecraft-1.4.1.uncached.zip
$ sha256sum Near_Future_Spacecraft-1.4.1.*zip
9392823e6690b412dc2c186df27f7bc226c2742f25d547482f40a5e20bf09360 Near_Future_Spacecraft-1.4.1.cached.zip
bd38e60132d72b3e6e8766eb583681b118f0c3946517711271a39502177fd739 Near_Future_Spacecraft-1.4.1.uncached.zip
A restart of ATS might be enough to fix this, especially with the storage problem solved, but this probably won't happen before tomorrow morning when @V1TA5 is back up again.
Hiya DasSkelett, thanks for the update :) Sounds like it might be an easy-fix(tm), fingers crossed. Good news hopefully.
Apologies for the tangent, @DasSkelett, but what do you think about adding a new Type:
label for outer layer infrastructure and reserving Backend
for Python code stuff inside of gunicorn?
Let's do that. Thought the same while picking labels, but was busy with other stuff and didn't want to spend much time organizing labels, so I picked the one that fitted best.
While we're on it, we could split the Type:
labels into to groups, I consider Backend / Frontend / Migration / Email / TheNewInfraOne different from Improvement / Bug / Feature / Question. Maybe the first group could be Area:
? Or we remove the prefixes from the second group completely?
Ha, I found a way to purge the zip from the ATS cache for all users! We can do it with a curl PURGE request from alpha or beta, apparently ATS doesn't care about where it's coming from. It should now serve the real, uncorrupted zip:
$ sha256sum Near_Future_Spacecraft-1.4.1.*zip
9392823e6690b412dc2c186df27f7bc226c2742f25d547482f40a5e20bf09360 Near_Future_Spacecraft-1.4.1.cached.zip
bd38e60132d72b3e6e8766eb583681b118f0c3946517711271a39502177fd739 Near_Future_Spacecraft-1.4.1.uncached.zip
bd38e60132d72b3e6e8766eb583681b118f0c3946517711271a39502177fd739 Near_Future_Spacecraft-1.4.1.now.zip
@Shades-McGee, please re-try the installation in CKAN, it should work now.
Well done @DasSkelett, it works... we're good to go. Thank you for the assist :)
We can do it with a curl PURGE request from alpha or beta
Now that's a neat trick! Did you just use curl
?
While we're on it, we could split the
Type:
labels into to groups, I consider Backend / Frontend / Migration / Email / TheNewInfraOne different from Improvement / Bug / Feature / Question. Maybe the first group could beArea:
? Or we remove the prefixes from the second group completely?
Makes sense to me, Type
is now Area
for those and Area: Infrastructure
now exists.
Now that's a neat trick! Did you just use
curl
?
Yup. I've extended it a bit and put it in a script now (/home/DasSkelett/bin/purge.sh
):
#!/bin/bash
ID=$@
CONTENT_URL=$(curl -ILs -o /dev/null -w %{url_effective} https://spacedock.info/mod/$ID/download)
CDN_IP=$(getent hosts web.52k | awk '{ print $1 }')
curl -IX PURGE --resolve spacedock.info:443:${CDN_IP} ${CONTENT_URL}
I want to put it somewhere in this repo or wiki to preserve it, just need to find a place.
The same corruption bug is also occurring with the following mods:
Near Future Aeronautics 2.1.0 (spacedock.info, 38.2 MiB) Near Future Launch Vehicles 2.1.3 (spacedock.info, 161.3 MiB)
Thanks, those two should be taken care of. Still hoping that @V1TA5 is going to restart ATS when he's online again, there might be many more hidden in the cache.
Description (What went wrong?):
While attempting to install the mod 'Near Future Spacecraft 1.4.1', a popup 'Error!' window appears with the following text...
... and then the following text appears in the 'Status log' tab in the CKAN window
Please note (from DasSkelett of KSP-CKAN/NetKAN) ticket #8590 - https://github.com/KSP-CKAN/NetKAN/issues/8590:
Reproduction Steps (What did you do?):
Go to 'Manage mods' tab in CKAN then select & attempt to install 'Near Future Spacecraft'
Expected Behavior (What do you think should have happened instead?):
I've successfully installed 'Near Future Construction/Electrical/Propulsion/etc.' with no issues.
Environment (OS/Browser/Plugins/etc):
Win 10 'Near Future Spacecraft 1.4.1'