[00:30] is the tracker migration just a rsync of '/' and when is it happening? [00:43] oh huh, slipped my mind [00:43] tomorrow, i think [00:43] about 24 hours from now [00:43] how long will the tracker be not available? [00:43] yeah [00:44] few hours, probably [00:44] ok [00:44] do you expect this to cause trouble? [00:44] maybe the new tracker should just start from scratch? [00:44] i'd like to build a new machine, yes [00:44] debian 6 is kind of old [00:44] it's way stale [00:44] no, I don't expect problems. just good to know when it'll be offline [00:45] ok, cool [01:09] starting from scratch also gives us an opportunity to doc it [01:09] or cross-check docs, etc. [01:11] good point [01:12] i'll see if i, as someone basically unfamiliar with how the tracker works, can set up a functioning one [09:11] *** GLaDOS has quit IRC (Read error: Operation timed out) [09:51] *** skiy has joined #warrior [09:53] *** skiy has quit IRC (Client Quit) [09:53] *** skiy has joined #warrior [09:53] *** skiy has quit IRC (Client Quit) [11:12] *** GLaDOS has joined #warrior [15:56] *** PanoIgano has joined #warrior [15:59] Hi guys, There is an issue with my Archive Team Warrior. I start it and connect normally to http://localhost:8001/ but I lose connection a few hours later. I am always working on the "ArchiveTeam's Choice". Do you experience something similar? [16:39] *** PanoIgano has quit IRC (Ping timeout: 240 seconds) [16:47] *** PanoIgano has joined #warrior [18:07] does it fix itself if you hit 'reload', PanoIgano ? [18:18] the code for reconnecting was commented out during the sockjs change. then the code got really messy after the status summary feature was added [19:39] @xmc yes it does! But since I have the laptop on 24/7 (most of the time is unattended) my warrior loses a lot of work that could have been done... [19:51] oh it'll work even if your browser isn't open [20:00] *** PanoIgano has quit IRC (Quit: Page closed) [20:17] *** chfoo has quit IRC (Remote host closed the connection) [20:22] *** chfoo has joined #warrior [22:13] crazy ideas [22:14] a pipeline file is loaded by seesaw via eval [22:14] I wonder if we could do hot code replace by just doing that over and over again [22:14] archivebot has gotten to the point where some sort of automatic hot-update would be really, really useful [22:15] actually wait it doesn't matter because it's not the pipeline that causes delays, it's huge jobs [22:15] forget I said anything [22:16] hmmm [22:16] semaphore the jobs [22:16] reload the bot [22:16] D: [22:41] *** skiy has joined #warrior [23:05] *** skiy has quit IRC (Leaving) [23:50] migration has been held up for a little while because i'm trying to figure out how to provision a box