| chetty: | morning | [02:30] |
| diana_coman: | server down | [04:27] |
| diana_coman: | I think it was me this time, sorry chetty | [04:27] |
| diana_coman: | I wanted to stop a craft and apparently it is not possible to do that anymore now (or at least not without crashing) | [04:27] |
| diana_coman: | it wasn't the bot, in any case, so it wasn't a matter of timing | [04:28] |
| chetty: | ok, back up, I'll look at the log | [04:33] |
| diana_coman: | thanks | [04:34] |
| chetty: | it has the same output as bad timing, but if you want to stop a craft best bet would be to move | [04:35] |
| diana_coman: | oh, that's a nice idea, didn't think of it | [04:35] |
| diana_coman: | will move next time then | [04:36] |
| chetty: | I think this is the first crash sine I threatened people yesterday :) | [04:37] |
| diana_coman: | ha ha, the chetty stick approach works then :D | [04:40] |
| diana_coman: | I've picked up and then dropped the toolkit so that hopefully it doesn't get sweeped away | [05:04] |
| chetty: | I dont think toolkits get swept, bit I would have to look up the stats on it to be sure | [05:07] |
| chetty: | and if you are standing next to it using it, its guarded and certainly doesnt getswept | [05:08] |
| diana_coman: | yeah, it wasn't mine, that's the thing | [05:17] |
| diana_coman: | I think it's mp's | [05:17] |
| diana_coman: | but since he got thrown out when the server crashed | [05:17] |
| diana_coman: | I picked it up and put it down to reset and give him a bit more time | [05:18] |
| diana_coman: | but well, I went away mining grass now | [05:18] |
| diana_coman: | I remember I lost 1 toolkit some time ago at a crash | [05:18] |
| diana_coman: | oh well | [05:19] |
| jurov: | hanbot still there? | [05:48] |
| chetty: | someone had stuck bot again? | [06:05] |
| jurov: | is offline | [06:07] |
| chetty: | server reset in 5 | [08:15] |
| chetty: | done | [08:25] |
| jurov: | chetty you use a fixed message for "server reset in 5"? | [08:39] |
| jurov: | so that bots can use that to wrap up | [08:39] |
| chetty: | well I try, but I do have the occasional typo when I do that | [09:17] |
| chetty: | I can use an autoated thing but then it would be on auto and I couldnt 'hold off a min so I | [09:18] |
| jurov: | ofc you can't always use it.. just asked if the message is consistent when you do | [09:20] |
| chetty: | yes, assuming I dont make a typo | [09:26] |
| jurov: | :) | [09:28] |
| jurov: | i have stuff saved in some craft tables that are in my inventory | [12:25] |
| jurov: | i dropped one table and clicked "take and stack all" | [12:26] |
| jurov: | it went very slowly (up to 10 sec/ item) | [12:26] |
| jurov: | and then crashed | [12:26] |
| jurov: | server | [12:26] |
| mircea_popescu: | nuts. | [12:32] |
| chetty: | up | [12:33] |
| chetty: | the crash came from dpb crafting, nothing to do with your craft-tables jurov | [12:36] |
| jurov: | still i saw at least once the craftbot going haywire over multiple crafting tables | [12:37] |
| chetty: | cool, we do survive bots doing bad stuff, sometimes | [12:38] |
| chetty: | server going down in 5 | [12:45] |
| mircea_popescu: | so I've been trying to do a 30 hour craft. for the past 20 hours it progressed to about 15\% complete. i'm well sick of the situation, i've had it with the crashes, server's going down and will stay down for a while, until chetty figures a structural way to fix all this. | [12:46] |
| mircea_popescu: | which will hopefully be something like a week. | [12:46] |
| mircea_popescu: | since can't have her running around with patches and also refactoring code, the server will stay down for the interval. | [12:47] |
| mircea_popescu: | the sunday event is moved to next sunday. | [12:47] |
| mircea_popescu: | tentatively, at least. | [12:47] |
| jurov: | so.. it will be down for maybe a week? | [12:53] |
| mircea_popescu: | it's going to be down for as long as it takes but in a week i'll re-evaluate the situation. | [12:56] |
| jurov: | hi diana_coman, check the logs :( | [15:00] |
| diana_coman: | yeah, I just did | [15:01] |
| diana_coman: | thanks jurov | [15:01] |
| diana_coman: | one week of break is not necessarily a bad thing anyway, esp if it means a more stable server afterwards; after going through the client code I can rather fully understand the need for taking the server down and focusing on making it structurally sound rather than trying to patch it | [15:22] |
| diana_coman: | it would be great though if there were perhaps some test server available for testing bots, but it can wait | [15:22] |
| jurov: | i have no idea in what kind of "structural way" can be mad c++ codebase fixed in a week | [15:27] |
| mircea_popescu: | diana_coman that's precisely what can't be had. because they will crash it. | [15:32] |
| diana_coman: | well, it's a *minimum* of 1 week from what I gather, isn't it? | [15:32] |
| mircea_popescu: | notrly. | [15:33] |
| diana_coman: | mircea_popescu thought so, sigh | [15:33] |
| diana_coman: | uhm, thought it was meant for 1 week down and then re-assessment? | [15:34] |
| diana_coman: | or not? | [15:34] |
| mircea_popescu: | it's a week soft. what's so hard to grok about that rly ? | [15:35] |
| mircea_popescu: | the specified interval exists strictly so you can not ask for a specified interval. it can not be on the other hand used against me in any manner - not as too long, nor as too short. | [15:35] |
| mircea_popescu: | ie, soft term. | [15:36] |
| diana_coman: | ie no term, ok | [15:38] |
| mircea_popescu: | nah, it's a week :D | [15:39] |
| jurov: | i understood it as there may be some more info in a week | [15:39] |
| mircea_popescu: | anyway, you can't refactor code while at the same time running around trying to patch it at random intervals multiple times a day | [15:46] |
| mircea_popescu: | sometimes multiple times an hour. | [15:46] |
| diana_coman: | well jurov, let me put it this way: from my point of view it is minimum 1 week, since I'm not going to plan now around a non-term that might be whatever | [15:46] |
| diana_coman: | mircea_popescu yes, of course | [15:47] |
| mircea_popescu: | how long it takes is notably also something you can't evaluate while at the same time running around trying to patch it at random intervals multiple times a day | [15:47] |
| jurov: | well, no other way if there is one and only one developer | [15:48] |
| mircea_popescu: | it'll have to fit in someone's head anyway. | [15:49] |
| mircea_popescu: | "one developer" thing's a complete orthogonal concern. | [15:49] |
| danielpbarron: | can finally catch up on logs and get that other machine working | [16:06] |
Comments feed: RSS 2.0