Autohosts operating non-downloadable engines - Page 2

Autohosts operating non-downloadable engines

Various things about Spring that do not fit in any of the other forums listed below, including forum rules.

Moderators: Moderators, Moderators

BigOof
Posts: 1
Joined: 20 Dec 2019, 19:47

Re: Autohosts operating non-downloadable engines

Post by BigOof »

Sorry for posting on an old thread, but I'd like to add to this:

Can confirm that I cannot download "spring 104.0.1-1333-gce618bd maintenance"
Currently an autohost bot is using said engine
Attempted to search for this engine manually via https://springrts.com/dl/buildbot/default/ | unable to find
1 x

User avatar
PicassoCT
Journeywar Developer & Mapper
Posts: 10261
Joined: 24 Jan 2006, 21:12

Re: Autohosts operating non-downloadable engines

Post by PicassoCT »

This is actually something that warrants a addition to lobby protocol. Forced surrender of server option controls by majority vote in a reasonable delayed time frame.
0 x

raaar
Metal Factions Developer
Posts: 824
Joined: 20 Feb 2010, 12:17

Re: Autohosts operating non-downloadable engines

Post by raaar »

some options:
- temporarily banning the autohost accounts until the issue is fixed
- restoring the engine versions so people can download them again
0 x

User avatar
PicassoCT
Journeywar Developer & Mapper
Posts: 10261
Joined: 24 Jan 2006, 21:12

Re: Autohosts operating non-downloadable engines

Post by PicassoCT »

The obvies solution make a autohost callable build bot that produces engines on demand
0 x

User avatar
ThinkSome
Posts: 297
Joined: 14 Jun 2015, 13:36

Re: Autohosts operating non-downloadable engines

Post by ThinkSome »

If the problem is engines taking up too much space on the server, then it can be solved without download issues by having the server act as an LRU reverse proxy cache for some other server that sits at someone's home.
0 x

User avatar
Silentwings
Moderator
Posts: 3613
Joined: 25 Oct 2008, 00:23

Re: Autohosts operating non-downloadable engines

Post by Silentwings »

Imo opinion a sane solution to this would be (1) uberserver writing a file somewhere specifying which engines recently (~within 1 week, say) were hosted on the server and (2) the disk cleanup scripts checking this file and not deleting stuff that is in use. Should be easy to do without filling the disk. Ofc (1) is dead easy and prs welcome, I don't even know where (2) lives/runs but iirc its just a python script?

The server (now) already has in-built tools for specifying when spring versions are to be forcibly discontinued.

Fyi this is low priorty for now, there are not many hosts involved and almost no one trying to use them.
0 x

User avatar
ThinkSome
Posts: 297
Joined: 14 Jun 2015, 13:36

Re: Autohosts operating non-downloadable engines

Post by ThinkSome »

Is someone even saving engine builds?
0 x

Google_Frog
Moderator
Posts: 2444
Joined: 12 Oct 2007, 09:24

Re: Autohosts operating non-downloadable engines

Post by Google_Frog »

Around 130 maintenance engines from 104.0.1-236-g23c7945 to 104.0.1-1455-g39f8fbd are stored on the Zero-K server. I copy them across manually with a web UI for testing and applying to the server. I don't know where they are stored, but they could surely be retrieved if required.
0 x

Post Reply

Return to “General Discussion”

cron