sankage
commented
7 years ago The system was setup to remove sigs older than 48 hours, but this was setup as a background job to be queued up on page refresh (to prevent the need to schedule tasks via cron job, and to just reuse the background system that was already there). Unfortunately while the background processes were having their meltdown the task was also not firing.
Taken from the original features/bugs issue. Text as follows:
the mapper miscalculates lifetimes on wh's i don't mean the too fast counter i mean the fact that it thinks an over 16hr old D382 connection has a stable life when in fact its eol after 12 hours and dead after 16. sig id GPV in screenshot, age 17 hrs life stable ???
Eol timers are based on Sig creation time in tripwire they auto update indeed. They are really handy on holes you roll yourself since your Sig start is correct on it. For the rest they are mainly handy when they are gone for sure. For instance if it's end of life in trip I don't trust the hole to be there and won't travel to it. Last night I went to three hs systems the first 2 had no wormhole and when I finally got in the c2 the connection was gone as well. That was rather frustrating since I wasn't expecting the mapper to be off that much.