| 00:04:08 | | jtagcat quits [Quit: Bye!] |
| 00:04:28 | | jtagcat (jtagcat) joins |
| 00:07:08 | <TheTechRobo> | JAA: I mean you could, just `LimitConcurrent` everything, isn't the concurrency exposed in the project files so you could default to it unless the user asked to use the project default concurrency? |
| 00:07:14 | <TheTechRobo> | (Awful solution, though) |
| 00:07:52 | <@JAA> | I'm not sure the concurrency is exposed, and yeah, awful as we'd have to change every project's code and add boilerplate for this to everything. |
| 00:33:08 | | brecheche quits [Remote host closed the connection] |
| 00:34:03 | | brecheche joins |
| 01:08:21 | | brecheche quits [Client Quit] |
| 04:31:55 | <tech234a> | Personally I was thinking recommended/max concurrent could be added to https://warriorhq.archiveteam.org/projects.json and parsed in the Warrior |
| 04:32:23 | <tech234a> | I was also thinking that the auto project could be turned into a list and if a project fails to start go to the next one in the list |
| 04:35:16 | <tech234a> | IDK if seesaw-kit changes are being reviewed at this point though |
| 04:35:43 | <tech234a> | *PRs to be more specific than "changes" |
| 04:40:39 | <vokunal|m> | Anyone have a fix for the error I showed above? It's still stuck on tracker 403 |
| 04:41:27 | <vokunal|m> | it's happening with every project |
| 04:43:19 | <vokunal|m> | here's the error the watchtower is spitting out. it cycles through every single project i have a container open for |
| 04:43:19 | <vokunal|m> | https://transfer.archivete.am/gHmfN/3wi%3B234.txt |
| 04:45:00 | <@JAA> | vokunal|m: What is your tracker nick? |
| 04:45:54 | <tech234a> | vokunal|m: could be a socket access error for Watchtower? make sure your user is in the correct user groups for Docker socket access or try using sudo |
| 05:00:14 | <vokunal|m> | Vokun |
| 05:01:02 | <vokunal|m> | I don't have to set a nick for the watchtower itself do i? |
| 05:09:04 | <@JAA> | No, tracker 403 and watchtower sound like two separate issues. I'm looking at the former, but no idea why you'd be getting that. |
| 05:51:15 | | brecheche joins |
| 05:51:21 | | brecheche quits [Client Quit] |
| 07:24:23 | | vantec quits [Read error: Connection reset by peer] |
| 08:13:36 | | vantec (vantec) joins |
| 08:27:50 | | woans quits [Ping timeout: 252 seconds] |
| 08:57:08 | | Dango360_ quits [Read error: Connection reset by peer] |
| 11:04:35 | | PredatorIWD_ joins |
| 11:04:53 | | vantec_ joins |
| 11:05:16 | | Letur6 joins |
| 11:05:29 | | monoxane quits [Client Quit] |
| 11:05:29 | | Letur quits [Quit: Ping timeout (120 seconds)] |
| 11:05:29 | | s-crypt quits [Quit: Ping timeout (120 seconds)] |
| 11:05:29 | | kiska quits [Quit: Ping timeout (120 seconds)] |
| 11:05:29 | | vantec quits [Remote host closed the connection] |
| 11:05:29 | | PredatorIWD quits [Remote host closed the connection] |
| 11:05:29 | | Letur6 is now known as Letur |
| 11:06:34 | | kiska (kiska) joins |
| 16:24:21 | | datechnoman quits [Quit: Ping timeout (120 seconds)] |
| 16:35:24 | | datechnoman (datechnoman) joins |
| 18:42:46 | | Transmission_Lost joins |
| 21:06:27 | | woans (WOANS) joins |
| 22:33:17 | | Dango360 (Dango360) joins |
| 22:41:29 | <vokunal|m> | I tried restarting the containers, the watchtower, deleting all containers and re making them, and restarting docker itself and nothing got rid of those errors. |
| 22:43:29 | | Iki1 joins |
| 22:46:56 | | AnotherIki quits [Ping timeout: 252 seconds] |
| 23:44:19 | | woans quits [Ping timeout: 265 seconds] |