00:45:24 heskitgel (L20 TeFi) Crash caused by signal #6: Aborted (Vaults:2) 01:35:37 Unstable branch on crawl.develz.org updated to: 0.32-a0-2093-gb660852781 (34) 01:58:14 Windows builds of master branch on crawl.develz.org updated to: 0.32-a0-2093-gb660852781 02:13:16 Unstable branch on cbro.berotato.org updated to: 0.32-a0-2093-gb660852781 (34) 02:55:22 Monster database of master branch on crawl.develz.org updated to: 0.32-a0-2093-gb660852781 06:33:20 Experimental (bcrawl) branch on underhound.eu updated to: 0.23-a0-5208-geafff8c3b6 06:33:32 <12asciiphilia> https://gall.dcinside.com/board/view/?id=rlike&no=465116 [TRANSLATED] (DCSS) I encountered a trunk error and didn't know where to post it, so I'm posting it here. It's on WebTiles trunk; I wrote this as soon as I saw it. This happened right after I went down the stairs to the Lair. I want to post the text, but I can't copy the log. 😦 06:33:57 <12asciiphilia> https://cdn.discordapp.com/attachments/747522859361894521/1272865723668103198/viewimage.png?ex=66bc8815&is=66bb3695&hm=be7df147e2b3edaa1aadecc413a4b936c71825ddbd1570350cf9a43633d28fd4& 06:52:34 <12ge0ff> Interesting, I can't reproduce this (yet): placing serial_demonic via &P on Lair:1 works w/o errors, even when this vault places hellwings 06:56:45 <12ge0ff> Although, this recently changed line looks suspicious: diff - 'red devil / hellwing w:5 / chaos spawn w:5 / ' .. + 'red devil / chaos spawn w:5 / hellwing w:1' .. <--- it looks like there's a missing / after "hellwing w:1" 07:00:33 <12ge0ff> Aha, I just had to be at the right depth to trigger this bug: it's reproducible when you try placing serial_demonic on D:9 10:13:49 <09gammafunk> yeah, pushing a fix 10:15:21 03gammafunk02 07* 0.32-a0-2094-gd22c55109e: fix: DES syntax in a serial vault (ASCIIPhilia) 10(2 minutes ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/d22c55109eef 10:15:48 <09gammafunk> @asciiphilia that should fix your bug, thanks for the report 10:15:51 03gammafunk02 07* 0.32-a0-2094-gd22c55109e: fix: DES syntax in a serial vault (ASCIIPhilia) 10(2 minutes ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/d22c55109eef 10:19:53 <09gammafunk> hrm 10:19:58 <09gammafunk> !issue 3977 10:19:59 <04Cerebot> https://github.com/crawl/crawl/issues/3977 10:20:20 <09gammafunk> concerning 12:12:52 <09gammafunk> I'm not sure if anyone has looked at this; I should try copying the save from CAO to reproduce locally 12:13:09 <09gammafunk> but I won't be able to try that for a while. If anyone wants to take a stab and needs the save, let me know 13:31:45 <04dracoomega> I could take a look at it. (I'm not sure there's enough to go on from that report otherwise, though.) 14:56:44 <09gammafunk> one sec, let me go copy save 15:00:15 <09gammafunk> ah yes, the nostalgic memory of running a find on a magnetic hard disk and it taking several minutes locate the file 15:11:39 <09gammafunk> @dracoomega let me know if this url works for you, CAO web server/download script seems to be fiddly in terms of the url working: https://crawl.akrasiac.org/saves/dumps/Velsharoon-issue3977.tar.bz2 15:14:28 <04dracoomega> Got it. (About 20 passwords later ^^; ) 15:15:08 <04dracoomega> My CAO credentials being something that presumably haven't been updated since the old days 15:15:53 <04dracoomega> "What password might I have been using 12 years ago?" >.> 15:16:42 <09gammafunk> always a fun game 15:17:09 <09gammafunk> hopefully I didn't incorrectly copy their 0.14 game or something 15:21:59 <04dracoomega> Well, I'll take a look once I finish breakfast 16:26:01 03DracoOmega02 07* 0.32-a0-2095-g86e73b92f4: Properly add dummy data for removed electroferric vorticies 10(61 seconds ago, 1 file, 1+ 0-) 13https://github.com/crawl/crawl/commit/86e73b92f46e 16:26:05 <04dracoomega> Fixed 16:27:06 03DracoOmega02 07* 0.32-a0-2095-g86e73b92f4: Properly add dummy data for removed electroferric vorticies 10(2 minutes ago, 1 file, 1+ 0-) 13https://github.com/crawl/crawl/commit/86e73b92f46e 16:29:50 <04dracoomega> ....for a second, I thought somehow the commit got doubled, but that's just the bot that's doubled >.> 16:30:44 <06pleasingfungus> i wonder if we should ban chei. 16:34:06 <08nicolae> agreed. too powerful. time to replace chei with another god. 16:39:01 <02Monkooky> I nominate NotChei as a replacemnet 16:51:56 <09gammafunk> Wow, it was just a missing axed mons 16:57:56 <09gammafunk> Feels like I'd have fixed it faster than the time it took me getting confused by cao's if I'd just looked at the error report carefully 16:58:13 <09gammafunk> I blame lack of gdb on cao 17:00:18 <12ge0ff> usually when Chei wakes up, there's a 100+ commit messages spam from the bot, which surprisingly didn't happen this time 17:02:25 <09gammafunk> We should just ban chei from the channel. I think |amethyst no longer has control over it 17:02:39 <09gammafunk> Literal rogue bot 17:03:12 <04dracoomega> Well, the crash dump is sadly quite nonspecific about what the problem is. I didn't immediately catch it until I had it print out the actual numerical ID of the supposed invalid monster. 17:07:30 <09gammafunk> it is a very thin dump, yeah. invalid monster + Air Elementalist -> air spells with removed monsters is an inference one might make though. Oh well, at least the save worked, thanks for the fix! 17:15:27 <09gammafunk> completely unrelated, I found -DCLUA_UNRESTRICTED_LIBS in clua.cc, which has proved to be useful. I had very slow execution times for a standard qw monster movement path check, and I really wanted to final do some basic "profiling". Probably I stopped putting off trying to do this since we also recently got a proper stack trace for clua. In any case, to profile we really needed to use "priveledged" libraries, specifically os, so we 17:15:28 could check system time to get execution time. 17:15:50 <09gammafunk> Just using the above define in compilation allowed the standard libraries to load in clua, including os 17:17:05 <09gammafunk> so that's a pretty good solution for people who need to do more with clua, and it's probably been sitting in the source as a solution for a long time. It just calls a standard lua library function when defined, so there's not really any special implementation either 17:18:07 <09gammafunk> Next I get to use it to write 1.2 million path debug messages to a text file so I can actually look it over properly instead of trying to examine slices of it in-game. Attempting to print them all in the usual way in the mesage log....did not go well 18:21:27 Unstable branch on crawl.akrasiac.org updated to: 0.32-a0-2095-g86e73b92f4 (34) 18:38:16 Unstable branch on underhound.eu updated to: 0.32-a0-2095-g86e73b92f4 (34) 19:33:42 03regret-index02 07* 0.32-a0-2096-g3ec762b4b6: Further loose tile edits and additions 10(7 minutes ago, 40 files, 32+ 6-) 13https://github.com/crawl/crawl/commit/3ec762b4b688 19:34:22 03regret-index02 07* 0.32-a0-2096-g3ec762b4b6: Further loose tile edits and additions 10(7 minutes ago, 40 files, 32+ 6-) 13https://github.com/crawl/crawl/commit/3ec762b4b688 20:08:05 <08nicolae> oooo, a plinth 20:08:10 <08nicolae> yeah i think the plinth will help with the cages 20:15:30 -!- ssm_ is now known as ssm 20:15:48 -!- ssm is now known as ssm_ 21:00:06 <09gammafunk> I can't enjoy these as a console player :berserk: 21:02:15 you just need to be creative with unicode 😛 21:04:59 <09hellmonk> is it intended that you can't get multiple berserk extensions off a single kill if you eg. kill something while both wearing bloodlust and wielding wrath of trog 21:06:44 it used to be, so if it still is it might be an oversight 22:40:04 <08nicolae> !scorepage 22:40:05 <04Cerebot> http://crawl.akrasiac.org/scoring/players/nicolae 23:17:58 <09gammafunk> @dracoomega I left a note for that user whose issue you fixed, since they were confused as to why the issue was closed. Generally good to leave a quick note mentioning that there's a fix and they just need to wait for a rebuild, since reporters don't always understand how commits/rebuilds work etc. 23:18:49 <09gammafunk> also I started a rebuild on CAO foolishly thinking it would be quick 23:18:52 <04dracoomega> Huh? I did that myself. 23:19:08 <04dracoomega> And I don't see one from you on github. Is this somewhere else? 23:19:21 <09gammafunk> looking at https://github.com/crawl/crawl/issues/3977 23:19:55 <04dracoomega> Oh. Oh, I thought they reopened the old issue, but I guess I responded to a new one. 23:20:09 <09gammafunk> ah, I see 23:20:38 <04dracoomega> (But I replied to them 5 hours ago and then they themselves closed it after confirming it was fine) 23:20:41 <09gammafunk> hah 23:20:43 <04dracoomega> I triggered a rebuild myself 23:20:45 <04dracoomega> Back then 23:21:15 <09gammafunk> weird, did they just file two issues or something? 23:21:50 <04dracoomega> It looks like after github automatically closed the first issue (due to the commit saying 'This fixes #so-and-so') they just made a new issue saying it wasn't fixed 23:21:58 <09gammafunk> nice, ok 23:22:00 <04dracoomega> But it was worded so similarly I thought they just updated the old one 23:22:11 <06pleasingfungus> good confusion 23:22:17 <04dracoomega> So I made CAO rebuild and then explained it to them 23:23:24 <09gammafunk> Well, disregard then I guess. Hard to have predicted they'd do that exact sequence of actions 23:24:12 <09gammafunk> which is prefect at hiding what happened as I read my emails 23:24:42 <09gammafunk> tbh I did have an email for the other issue where you responded but I guess I mentally ignored it 23:26:03 <04dracoomega> Hmmm, I suppose this is the issue with github closing them on its own; it doesn't actually link to or indicate the commit that caused it to close, does it? 23:26:11 <04dracoomega> In terms of "This was fixed by X" 23:26:26 <09gammafunk> it does actually 23:26:30 <09gammafunk> in the first one 23:26:36 <09gammafunk> the one I responded to 23:27:04 <09gammafunk> so your commit closed that one, and they posted the "Closed why?" message afterwords and opened a new duplicate issue 23:27:41 <09gammafunk> https://cdn.discordapp.com/attachments/747522859361894521/1273120834726133821/image.png?ex=66bd75ac&is=66bc242c&hm=d940b05bd6378dada8fe65162c7fa766671b0c2ca29b58a68abd8f453c63262d& 23:27:45 <09gammafunk> if that's what you're asking about 23:28:32 <04dracoomega> Oh, huh. Easy not to notice I guess 23:28:46 <04dracoomega> Like, the link to the actual fix, I mean 23:29:19 <09gammafunk> oh, I see what you mean, yeah github is generally good about always linking hashes everywhere 23:31:29 Unstable branch on crawl.akrasiac.org updated to: 0.32-a0-2096-g3ec762b4b6 (34)