HomeSearchPrevious dayNext day

00:08:25Bleo182600722719623455222 quits [Quit: The Lounge - https://thelounge.chat]
00:36:12nexussfan (nexussfan) joins
00:36:25nexussfan quits [Client Quit]
00:51:11Bleo182600722719623455222 joins
03:16:27@imer quits [Killed (NickServ (GHOST command used by imer9))]
03:17:40Max_G quits [Quit: Bye Bye]
03:18:20imer (imer) joins
03:18:20@ChanServ sets mode: +o imer
03:50:13nexussfan (nexussfan) joins
03:51:21wotd quits [Quit: connection go boom]
05:04:40n9nes quits [Ping timeout: 256 seconds]
05:06:54n9nes joins
05:32:04DogsRNice quits [Read error: Connection reset by peer]
05:36:59Shard11 quits [Ping timeout: 272 seconds]
05:43:54sec^nd quits [Remote host closed the connection]
05:44:07sec^nd (second) joins
05:45:10Shard11 (Shard) joins
06:03:07nexussfan quits [Client Quit]
07:34:34IDK quits []
07:34:56IDK (IDK) joins
08:40:37michaelblob quits [Quit: yoop]
08:41:47michaelblob joins
08:43:04<@arkiver>Guest: what is this for exactly?
08:44:22<@arkiver>picking a project to work on giving certain variables?
08:45:12<@arkiver>the URLs project will never be a default Warrior project due to a risks with the URLs going through there
08:46:49<@arkiver>perhaps something similar to this could be done, would likely be a separate project pulling a config file from the tracker, then setting/deciding which project to run.
08:50:11<@arkiver>a - for now - simpler version would be to set percentages on the tracker (in that config file) that represent the fraction of warrior that should run project x/y/z/etc.
08:54:16<@arkiver>the warrior would periodically (or maybe depending on a flag set on the tracker) redraw a new project using the assigned fractions.
08:54:44<@arkiver>could be optimize by taking the difference between the "target fraction" and the "current actual fractions" and switching depending on that, that would reduce the back and forth switching significantly.
08:54:59<@arkiver>optimized*
08:55:45<@arkiver>with that last bit of using difference between target and actual fractions, we can also incorporate decisions made using other factors like location, free disk, etc., but that would come later
08:57:15<@arkiver>Guest: and what is the 404 stuff about? i don't get why that is in there. CPU also unclear
09:02:30<@arkiver>i can give it a try in the coming days to see how "implementable" this is in our current structure
09:32:35Shard11 quits [Remote host closed the connection]
09:45:57Shard11 (Shard) joins
10:26:01<klea>I suppose Guest means to allow a project to stop running on warriors it's been banned in for a while
10:35:03daftaupe joins
10:48:51Shard11 quits [Client Quit]
10:52:55Shard11 (Shard) joins
11:46:26simon816 quits [Remote host closed the connection]
11:50:42simon816 (simon816) joins
12:00:02Bleo182600722719623455222 quits [Quit: The Lounge - https://thelounge.chat]
12:02:46Bleo182600722719623455222 joins
14:29:38Shard11 quits [Read error: Connection reset by peer]
14:36:46Shard11 (Shard) joins
14:47:26nexussfan (nexussfan) joins
14:49:31nexussfan quits [Read error: Connection reset by peer]
14:50:24nexussfan (nexussfan) joins
14:52:28nexussfan quits [Client Quit]
15:08:49nexussfan (nexussfan) joins
16:29:17cyanbox_ joins
16:31:13cyanbox quits [Ping timeout: 272 seconds]
17:57:27kansei- quits [Quit: ZNC 1.10.1 - https://znc.in]
18:05:06kansei (kansei) joins
18:09:44fuzzy80211 quits [Read error: Connection reset by peer]
18:11:00fuzzy80211 (fuzzy80211) joins
18:12:12Sluggs quits [Excess Flood]
18:16:49Sluggs (Sluggs) joins
18:25:52Sluggs quits [Excess Flood]
18:29:34Sluggs (Sluggs) joins
18:43:26bladem (bladem) joins
19:33:10nexussfan quits [Quit: Konversation terminated!]
20:43:47nexussfan (nexussfan) joins
22:09:41FiTheArchiver joins
23:18:59FiTheArchiver quits [Remote host closed the connection]
23:19:20FiTheArchiver joins
23:33:01wotd joins
23:43:09FiTheArchiver quits [Ping timeout: 272 seconds]

HomeSearchPrevious dayNext day