00:39:32systwi quits [Ping timeout: 252 seconds]
00:39:43systwi_ (systwi) joins
00:44:12systwi_ is now known as systwi
05:32:08Barto quits [Ping timeout: 252 seconds]
06:00:51IDK (IDK) joins
06:09:26pabs quits [Ping timeout: 265 seconds]
06:12:02pabs (pabs) joins
06:27:54spirit quits [Client Quit]
07:43:23JackThompson3 quits [Ping timeout: 252 seconds]
07:46:22JackThompson3 joins
10:59:46drin joins
11:02:30geezabiscuit quits [Ping timeout: 252 seconds]
11:02:30drin is now known as geezabiscuit
11:05:33drin joins
11:09:13geezabis- joins
11:09:35geezabiscuit quits [Ping timeout: 265 seconds]
11:10:02geezabis- is now known as geezabiscuit
11:11:50drin quits [Ping timeout: 252 seconds]
11:19:10drin joins
11:21:44geezabiscuit quits [Ping timeout: 252 seconds]
11:21:44drin is now known as geezabiscuit
17:13:48yano quits [Quit: WeeChat, the better IRC client, https://weechat.org/]
17:16:44yano (yano) joins
18:51:08Barto (Barto) joins
19:18:00<pokechu22>https://archive.org/details/archiveteam_archivebot_go_20230612000720_85add87c - it looks like this never had CDX files derived for it, any idea what happened there?
19:30:39pabs quits [Read error: Connection reset by peer]
19:47:38<Jake>pokechu22: still being derived. "this item is currently being modified/updated by the task: derive"
19:48:46<pokechu22>It wasn't showing that earlier (and it looks like e.g. https://archive.org/details/archiveteam_archivebot_go_20230612134528_5b4b9010 isn't showing it still)... but I'm guessing there's just a large backlog of stuff that's queued for being derived but hasn't started being derived yet
19:49:34<@JAA>Yeah, there are over 10k waiting derive tasks currently.
19:50:22<nicolas17>IIUC that particular derive task was queued 13 hours ago but only started running 15 minutes ago
19:51:05<@JAA>For archiveteam_archivebot_go_20230612000720_85add87c, correct.
19:51:36<@JAA>The one for archiveteam_archivebot_go_20230612134528_5b4b9010 was only queued 35 minutes ago, so it'll be a while until that runs.
19:53:10<Jake>yup ^
20:00:15<@JAA>A derive of mine is approaching one week of runtime. :-|
20:08:02driib quits [Quit: The Lounge - https://thelounge.chat]
20:08:52driib (driib) joins
20:35:09driib quits [Remote host closed the connection]
20:35:34driib (driib) joins
20:49:55driib quits [Remote host closed the connection]
20:50:19driib (driib) joins
21:08:02geezabiscuit quits [Ping timeout: 252 seconds]
21:09:49geezabiscuit (geezabiscuit) joins
21:10:49<masterX244>Whats deriving for over a week?
21:11:01<masterX244>Fat-ass warc cargo-train?
21:13:56<@JAA>The charm.li torrent at over 700 GiB.
21:15:36<@JAA>Took some 34 hours to download, 65 hours to recheck (oof), some copying around, now it's hashing since 30 hours, then there'll be the copy to the mirror. Lots of fun.
21:43:29<fireonlive>ooof
22:37:22<@arkiver>JAA: it's making progress at least
22:37:29<@arkiver>why worry about the speed a lot?
22:37:36<@arkiver>it'll be done
22:39:09<@arkiver>i wonder if there's some settings to set chunk size or whatever when hashing
22:39:15<@arkiver>perhaps it's inefficiently reading from disk
22:49:56<@JAA>arkiver: Not worrying about it, just surprised how long it takes. And yeah, I imagine the hashing is done somewhat inefficiently. It does compute three different hashes at once though.
23:18:54pabs (pabs) joins