#urlteam 2017-05-18,Thu

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***marvinw_ has quit IRC (Leaving)
marvinw has joined #urlteam
[00:00]
................................. (idle for 2h43mn)
nuc has joined #urlteam
nuc is now known as Somebody2
[02:44]
Somebody2OK, I'm back. IRC client died.
And I see that the tracker is stuck. Fixing now.
Hm, gg-gg 1ugb6 was throwing 502 errors, but it worked for me (albeit with a laughably long URL as the target)
ok, the tracker should be running again
looks like it got stuck at 2017-05-17 00:34:58.819013
[02:45]
Odd0002Somebody2: is there a reason it gets stuck? [02:54]
Somebody20dd0002 -- it is programmed to stop if there are too many error reports [02:56]
Odd0002ah [02:56]
Somebody2which is a Good Idea, because it means that something is happening, and having a human look is useful [02:56]
Odd0002that makes sense [02:56]
Somebody2but that requires a human actually look, and there aren't many of us active [02:56]
Odd0002I thought it would just randomly stop for no reason or something
and then you have to debug the code or something
[02:56]
Somebody2Nope, not that bad.
I usually explain what happened, as above, where I mentioned 1ugb6
[02:57]
Odd0002ok, good to know then [02:58]
Somebody2You can look at the tracker code -- look up terroroftinytown [03:00]
............... (idle for 1h11mn)
chfoothe older tracker was managed manually, meaning someone needed to generate the list of links and upload it to the tracker. this new tracker automatically generates the links which makes it easier to maintain but it makes it easy to forget about it. so that's why it is programmed to stop automatically on errors
it ensures that someone is always monitoring it to make sure we aren't hitting a server too hard
[04:11]
Somebody2the older tracker required manual pre-generation of shortcodes? interesting. [04:23]
.... (idle for 17mn)
***Odd0002 has quit IRC (Remote host closed the connection) [04:40]
.... (idle for 18mn)
Sk1d has quit IRC (Ping timeout: 250 seconds) [04:58]
Sk1d has joined #urlteam
mls has quit IRC (Ping timeout: 250 seconds)
[05:05]
....... (idle for 33mn)
mls has joined #urlteam [05:42]
.... (idle for 17mn)
svchfoo1 has quit IRC (Ping timeout: 370 seconds)
svchfoo1 has joined #urlteam
svchfoo3 sets mode: +o svchfoo1
[05:59]
............................ (idle for 2h17mn)
Jonison has joined #urlteam [08:17]
............................................................. (idle for 5h0mn)
VADemon has quit IRC (Read error: Connection reset by peer) [13:17]
.............. (idle for 1h6mn)
VADemon has joined #urlteam [14:23]
........ (idle for 37mn)
mls has quit IRC (Ping timeout: 250 seconds) [15:00]
mls has joined #urlteam [15:08]
............. (idle for 1h0mn)
dashcloud has quit IRC (Ping timeout: 250 seconds) [16:08]
dashcloud has joined #urlteam
svchfoo3 sets mode: +o dashcloud
[16:17]
.... (idle for 15mn)
Odd0002 has joined #urlteam [16:33]
.................................... (idle for 2h58mn)
dashcloud has quit IRC (Read error: Connection reset by peer)
dashcloud has joined #urlteam
svchfoo3 sets mode: +o dashcloud
[19:31]
mls has quit IRC (Ping timeout: 250 seconds) [19:37]
Jonison has quit IRC (Quit: Leaving) [19:47]
............................. (idle for 2h21mn)
Sk1d has quit IRC (Ping timeout: 194 seconds) [22:08]
Sk1d has joined #urlteam [22:13]
.... (idle for 16mn)
dashcloud has quit IRC (Remote host closed the connection) [22:29]
dashcloud has joined #urlteam
svchfoo1 sets mode: +o dashcloud
[22:37]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)