00:25:22 -!- Rast-- is now known as rast 01:41:05 the docs recommend that new contributors bring up even small changes in this channel, so hello, I'm new 01:41:22 I have a two-line change to make wanderers start with their weapon on 'a' like everyone else 01:42:07 if no one immediately yells "stop, you fool" I will submit a pull request 01:42:13 sounds reasonable, fourba. a PR is the way to go 01:42:40 excellent. PR incoming 01:45:41 New branch created: pull/1006 (1 commit) 13https://github.com/crawl/crawl/pull/1006 01:45:41 03Joshua Gelbard02 07https://github.com/crawl/crawl/pull/1006 * 0.24-a0-171-g86426b9: Start new wanderers with weapon in slot 'a' 10(88 minutes ago, 1 file, 3+ 0-) 13https://github.com/crawl/crawl/commit/86426b9b9139 02:59:06 Monster database of master branch on crawl.develz.org updated to: 0.24-a0-170-gd8427f5 03:43:28 -!- amalloy is now known as amalloy_ 03:52:10 Fork (bcadrencrawl) on crawl.kelbi.org updated to: 0.22.1-81-g71e6c3b714 04:15:43 if I have another tiny change, should I submit separate a pull request or just push it to my existing one? 04:16:02 it's unrelated, but I really do mean tiny. someone was missing an exclamation point. 04:16:58 (merfolk were making splash sounds when they dropped stuff into water and the rest of us weren't, which is the opposite of what was meant to happen) 04:39:22 I'd say a separate PR fourba 04:41:43 cool, thanks 04:46:49 New branch created: pull/1007 (1 commit) 13https://github.com/crawl/crawl/pull/1007 04:46:49 03Joshua Gelbard02 07https://github.com/crawl/crawl/pull/1007 * 0.24-a0-171-gd197e03: Fix splash noises when dropping item into water 10(89 minutes ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/d197e0349e5b 05:04:04 -!- TabMasher is now known as Euph0ria 09:24:09 Stable (0.22) branch on underhound.eu updated to: 0.22.1-57-g7394efd48c 10:45:04 just wanted to let you know that stone-soup on arch linux is still on 0.22, no idea whats up with the maintainer, it's been a month now. anyway just so you know :) 10:46:40 Expectations are different in the Arch world to the Debian world, I see. :-) 10:47:27 cataclysm 0.d got updated within one day 10:49:26 maybe the maintainer is on an extended vacation :P 10:49:43 I'm pretty sure Debian no longer has Linley Crawl 10:50:27 I guess few people working on Arch are actually obligated to do anything on any schedule. Or are there people actually getting paid to maintain packages? 10:50:51 Chousuke: It's a volunteer effort AFAIK. 10:58:25 https://aur.archlinux.org/packages/crawl/ appears to show 0.23.0 10:59:07 fwiw 0.23.1 has an issue that may make life difficult for downstream package maintainers, it'll be backed out in 0.23.2 but that could be slowing things down 11:00:18 oh I guess joemaro left 13:29:00 Wolf spider breaks autoexplore 13https://crawl.develz.org/mantis/view.php?id=11924 by Pekkekke 19:56:38 -!- amalloy_ is now known as amalloy 20:31:48 floraline: not sure why, but I can't seem to spectate my game in webtiles 20:31:53 and the lobby seems to struggle to load as well 20:33:42 -!- glaas` is now known as glaas 21:30:56 gammafunk: try saving and reloading your game 21:32:33 if you're playing on console, there is an issue where the webtiles lobby sometimes fails to read from the console game socket resulting in that game either not appearing or not allowing spectate 21:34:12 i have not been able to figure out what is causing this 21:34:25 i have some ideas for some changes that could make it less likely to happen but that isn't a great solution 21:43:21 ebering gammafunk silver rune isnt in my v:5 21:43:59 and... i reopened my game and its there 21:49:35 this is the first i'm hearing of the lobby being slow, is it consistent? 21:50:11 I haven't tried it much more than this one time 21:50:11 just wanted to get a screenshot of the minimap 21:50:16 I forget if I've tried to stream on twitch from cko, possibly not 21:50:26 it's something like a 1 in 7 chance that a console game will not appear in webtiles when started 21:50:34 interesting, I'll keep that in mind 21:50:42 some failure related to the socket on disk that webtiles wants to read from 21:50:52 yeah, one thing I noticed is that the reported idle time was over 30 minutes out of date 21:50:58 it said I had been idle for 36 minutes 21:51:04 yeah i think that's due to the same issue 21:51:07 or something along those lines 21:51:13 somehow it does know a game is going on but it has no info on it 21:52:31 a webtiles PR might be able to hide this issue but it's frustrating to not know the root cause 21:55:49 floraline: yeah, seems to be happening again now 21:55:52 can you spectate me on cko? 21:56:00 nope 21:56:05 it seems to load the chat as I see the chat window + 2 spectators 21:56:09 yet it stays at loading 21:56:17 yeah, see you in chat as well 21:56:29 and chat does work, weird 21:56:39 yeah, see your message as well 21:57:00 wonder if just reconnecting will get it to work eventually 21:57:14 ah, indeed 21:57:23 I saved in ssh and hit play again 21:57:26 then I could spectate 21:57:44 and it seems to spectate normally 21:57:45 yep 21:57:56 well at least I know that it can be made to work eventually, helpful if I try to stream 21:57:59 i'm trying to find the line of code that fails, i found it before 21:58:07 yeah it's an easy workaround thankfully 21:58:11 but still super frustrating 21:58:30 as far as i can tell, spectating from the console side works just fine 22:00:09 i think it's this line that fails: https://github.com/crawl/crawl/blob/master/crawl-ref/source/webserver/connection.py#L98 22:00:30 during connect() in this same class 22:01:10 yeah, that's just the very general method to send a json message 22:01:21 it's more that we don't know the conditions that are causing failur 22:01:22 e 22:01:35 right 22:02:30 i was thinking some better error handling there could queue it for a retry or something 22:22:10 floraline: well, that's something that affects every single message sent, so you have to be careful about its behaviour 22:22:16 it would be much better if we knew what exactly was happening 22:22:40 otherwise you're sort of randomly trying various retries without knowing the underlying cause, and you can just end up creating new bugs 23:33:32 -!- amalloy is now known as amalloy_