#urlteam 2014-07-07,Mon

↑back Search

Time Nickname Message
00:00 🔗 deathy maybe you can check the status of that one. only 3 minutes between tracker giving it and denying.
00:49 🔗 db48x deathy: what's your ip address?
00:55 🔗 deathy the one where that came from: 104.131.136.95
00:55 🔗 deathy it's a droplet at DO
00:55 🔗 db48x hmm
00:56 🔗 db48x there just isn't enough information to tell for sure, but that does eliminate one of the long-shot possibilities
00:56 🔗 deathy in US somewhere. Denied I mentioned some hours ago was from another DO droplet in Amsterdam
00:56 🔗 db48x I think the tracker must have a race condition where it can assign a task and then immediately reassign it
00:58 🔗 db48x so some percentage of the time your ip address won't match what's in the database, and it'll reject it
00:58 🔗 deathy seems likely/logical.
00:59 🔗 db48x the hilarious thing is that by the time it's done that it's already written the body of your response to disk
00:59 🔗 deathy just checked last ~6-ish tasks * 4 machines and didn't see that message.
01:00 🔗 deathy tracker traffic slower now maybe?
01:01 🔗 deathy might be something to look into if we still want more and more clients..
01:01 🔗 deathy where exactly is tracker on github? just in case I have time to randomly look around..
01:02 🔗 db48x db48x/tinyarchive
01:02 🔗 db48x the code is tracker/tracker.py
01:03 🔗 db48x the other possibility is that when it goes to create a file to hold the data you're uploading (which is in the body), it creates the randomly-named temporary file but there's already one with the same name
20:55 🔗 deathy looks to be going/working well as items processed
20:57 🔗 deathy but does it actually find any URLs? most I see are "found 0 URLs"
21:03 🔗 db48x we may have found them all already
21:04 🔗 db48x apparently we've found 2.2 million though
21:18 🔗 deathy 12930 finished in last 24 hours. available: 23206, looking good.
21:22 🔗 db48x you're winning

irclogger-viewer