<Darklight[m]>
This was an actual issue during the upgrade but I should be able to work it out for you
<Darklight[m]>
Hrmmm, it works locally and spacedock's test instance also seems to work, but I can definitely see your one is broken
<Darklight[m]>
<span class="d-mention d-user">HebaruSan</span> this one has me confused - I managed to do the banner upload just fine on my local test instance, and then alpha, and then I decided to test actual spacedock and it all seems fine. Inside cukkoo's user profile is a zero byte file of the thumbnail with no source image there
<Darklight[m]>
I wonder if the image format is weird, cukkoo do you have the mod image lying around somewhere I could test with?
HebaruSan[m] has joined #spacedock
<HebaruSan[m]>
Is it the alpha channel thing that <span class="d-mention d-user">DasSkelett</span> is fixing maybe?
<Darklight[m]>
I'll see if I can upload from my end and go through the logs for the exact error
<Darklight[m]>
Because I can definitely see you're not the only one with the problem, there is black all over spacedock >.<
<Darklight[m]>
Well that's annoying, it worked for me... one sec
<Darklight[m]>
<span class="d-mention d-user">HebaruSan</span> I think it works if you drag the image in the header to a different X position
<Darklight[m]>
I'll try that locally, I think I dragged when testing on the local thing
<Darklight[m]>
It's probably as simple as "initialise the X offset to 0" if we don't do that
<Darklight[m]>
Local test instance doesn't want to recreate the bug
<cukkoo[m]>
ok but some mod arent broken
<cukkoo[m]>
like dark multiplayer
<Darklight[m]>
That's my mod, but that's because I uploaded that 5 years ago or however long spacedock has been around 😛
<cukkoo[m]>
Oh
<Darklight[m]>
I think I should look through production logs, maybe they will tell me something (Vitas and I are the only ones who can do that, vitas is the one actually running spacedock)
<Darklight[m]>
Admins have the ability to edit mods, I managed to upload that pic on yours
<cukkoo[m]>
then how to get the log
<Darklight[m]>
Something on the server end, tis all good 😉
<Darklight[m]>
thumbnail.py was apparently my creation and I had completely forgotten I even wrote it
<Darklight[m]>
I think I did that because I complained about my australian internet and the site taking a long time 😛
<cukkoo[m]>
So spacedock is host in australia
<cukkoo[m]>
oh
<Darklight[m]>
Germany
<Darklight[m]>
HebaruSan I guess we should bug vitas about an upgrade window after that is merged. The code was probably older than time itself so you're definitely right about renaming that parameter to PIL.Image.LANCZOS
VITAS[m] has joined #spacedock
<VITAS[m]>
the problem with black thumbnails has to do with png having alpha channels
<VITAS[m]>
the converter screws up and also appends whatever file exte. the source has instead of jpg. as HebaruSan said DasSkelett fixed it in a newer build
<VITAS[m]>
i wont be at home for the next 2-3 weeks so i would rather not edeploy new sd versions during that time. i also want to find ways to prevent the problems we had the last 2 times with stuff not working with prod data first (e.g. seeding test db and unit tests)
HebaruSan[m] has quit [Quit: Idle timeout reached: 10800s]
cukkoo[m] has quit [Quit: Idle timeout reached: 10800s]
Darklight[m] has quit [Quit: Idle timeout reached: 10800s]
RockyTV[m] has joined #spacedock
<RockyTV[m]>
I've seen some PRs and new issues but what's been going on? work has kept me busy for a few weeks
<VITAS[m]>
HebaruSan: does a good job at keeping github up to date
<VITAS[m]>
how is work?
<RockyTV[m]>
it's good, now that the training is over most times I'm working with react and leaflet (js map library), and I am surprised that the company accepted my suggestion to use leaflet instead of the ArcGIS map library
<VITAS[m]>
i supose you had good arguments
<VITAS[m]>
webdev isnt something new for you after all
<VITAS[m]>
and they notice
RockyTV[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
HebaruSan[m] has joined #spacedock
<HebaruSan[m]>
Are old home dirs on alpha and beta archived? I don't think I had anything critical on there but not sure
DasSkelett[m] has joined #spacedock
<DasSkelett[m]>
Nope, just copied the `authorized_keys`. I considered copying the whole home directory, but it looked like you had a full separate clone of the SD repo in there or so, and I didn't want to blow up the backup ^^
<DasSkelett[m]>
Maybe <span class="d-mention d-user">VITAS</span> has the old containers still around though.
<HebaruSan[m]>
Ahh OK. No worries, the only thing I miss is that `spy.c` program, and I can just re-install that
<HebaruSan[m]>
It's nice to see whether you're already logged on, when I'm deciding whether to mess around with restarting
<DasSkelett[m]>
Hehe
<DasSkelett[m]>
(We should definitely find a better way to do this in the future, maybe woth an Ansible script as VITAS proposed, because it's quite tedious to do manually)
<HebaruSan[m]>
It might be nice to have a shared home volume for both alpha and beta, so any file we place is automatically on both
<DasSkelett[m]>
Good idea
<DasSkelett[m]>
Maybe we should create a new SpaceDock-Scripts repo which contains all those deployment scripts we aggregate, which don't necessarily fit into the main repo.