| 00:21:14 | | atphoenix_ quits [Remote host closed the connection] |
| 00:21:55 | | atphoenix_ (atphoenix) joins |
| 00:39:42 | | G4te_Keep3r34924 joins |
| 00:47:00 | | G4te_Keep3r34924 quits [Client Quit] |
| 00:59:02 | | G4te_Keep3r34924 joins |
| 01:25:04 | <@JAA> | I don't understand why the VirusCheck book_op.php task always takes so long, especially on tiny uploads. |
| 01:28:16 | <@JAA> | Over 5 minutes to check a 200-byte upload is at least 5 minutes too long. |
| 01:35:51 | | HP_Archivist quits [Quit: Leaving] |
| 02:17:12 | <yzqzss> | +1 |
| 02:22:22 | <yzqzss> | ia tasks -p 'cmd:book_op.php' | jq | grep submitter | sort -n | uniq -c | sort -n | tail |
| 02:28:51 | <fireonlive> | maybe they need to upgrade their version of norton antivirus |
| 02:52:32 | <TheTechRobo> | Based on logs of items that were detected as malware, I'm pretty sure they use VirusTotal |
| 02:52:41 | <TheTechRobo> | I don't think VirusTotal takes 5 minutes |
| 05:05:43 | | nulldata quits [Client Quit] |
| 05:06:44 | | nulldata (nulldata) joins |
| 06:02:26 | | Arcorann (Arcorann) joins |
| 08:00:51 | | sepro quits [Read error: Connection reset by peer] |
| 08:03:38 | | sepro (sepro) joins |
| 12:42:15 | | Arcorann quits [Ping timeout: 272 seconds] |
| 13:15:58 | <@JAA> | > rsync: write failed on "/26/items/stackexchange_20240305/stackoverflow.com-PostHistory.7z": No space left on device (28) |
| 13:16:01 | <@JAA> | oh no |
| 13:23:28 | | nulldata quits [Ping timeout: 255 seconds] |
| 14:22:00 | | qwertyasdfuiopghjkl quits [Ping timeout: 265 seconds] |
| 14:42:45 | | HP_Archivist (HP_Archivist) joins |
| 14:54:07 | | nulldata (nulldata) joins |
| 14:56:49 | <@arkiver> | JAA: it might shuffle data around to fix that |
| 15:05:08 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 15:43:52 | | threedeeitguy39 quits [Ping timeout: 255 seconds] |
| 16:12:03 | | threedeeitguy39 (threedeeitguy) joins |
| 16:23:05 | <@JAA> | Yeah, we'll see. |
| 16:24:48 | <@JAA> | This wasn't a cry for help (yet). :-) |
| 16:39:06 | <@arkiver> | JAA: if it creates a redrow, someone will eventually look at it and fix whatever needs fixing |
| 16:39:26 | <@arkiver> | usually redrows are not unique, there's processes already going on to fix a big percentage of them automatically (clearing space for examplw) |
| 16:40:34 | <@JAA> | Indeed :-) |
| 16:42:35 | <@JAA> | It is a redrow. I don't see any shuffle tasks or similar currently, but I'll just let it do its thing and check back later or tomorrow. |
| 18:03:05 | | fireonlive wonders if IA uses 'slack' or something internally |
| 18:17:13 | <@JAA> | arkiver: It got unstuck, but now stackexchange_20240305 triggered the malware check on monero.stackexchange.com.7z and reverseengineering.stackexchange.com.7z. (Not the first time this happened, I believe; the same thing blocked the upstream stackexchange item a couple years ago IIRC.) |