00:25:22 -!- Rast-- is now known as rast
01:41:05 <fourba> the docs recommend that new contributors bring up even small changes in this channel, so hello, I'm new
01:41:22 <fourba> I have a two-line change to make wanderers start with their weapon on 'a' like everyone else
01:42:07 <fourba> if no one immediately yells "stop, you fool" I will submit a pull request
01:42:13 <amalloy> sounds reasonable, fourba. a PR is the way to go
01:42:40 <fourba> excellent. PR incoming
01:45:41 <Cheibriados> New branch created: pull/1006 (1 commit) 13https://github.com/crawl/crawl/pull/1006
01:45:41 <Cheibriados> 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 <Gretell> 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 <Kelbell> Fork (bcadrencrawl) on crawl.kelbi.org updated to: 0.22.1-81-g71e6c3b714
04:15:43 <fourba> if I have another tiny change, should I submit separate a pull request or just push it to my existing one?
04:16:02 <fourba> it's unrelated, but I really do mean tiny. someone was missing an exclamation point.
04:16:58 <fourba> (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 <NP7> I'd say a separate PR fourba
04:41:43 <fourba> cool, thanks
04:46:49 <Cheibriados> New branch created: pull/1007 (1 commit) 13https://github.com/crawl/crawl/pull/1007
04:46:49 <Cheibriados> 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 <Lantell> Stable (0.22) branch on underhound.eu updated to: 0.22.1-57-g7394efd48c
10:45:04 <joemaro> 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 <Pinkbeast> Expectations are different in the Arch world to the Debian world, I see. :-)
10:47:27 <joemaro> cataclysm 0.d got updated within one day
10:49:26 <Chousuke> maybe the maintainer is on an extended vacation :P
10:49:43 <Pinkbeast> I'm pretty sure Debian no longer has Linley Crawl
10:50:27 <Chousuke> 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 <Pinkbeast> Chousuke: It's a volunteer effort AFAIK.
10:58:25 <advil> https://aur.archlinux.org/packages/crawl/ appears to show 0.23.0
10:59:07 <advil> 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 <advil> oh I guess joemaro left
13:29:00 <Cheibriados> 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 <gammafunk> floraline: not sure why, but I can't seem to spectate my game in webtiles
20:31:53 <gammafunk> and the lobby seems to struggle to load as well
20:33:42 -!- glaas` is now known as glaas
21:30:56 <floraline> gammafunk: try saving and reloading your game
21:32:33 <floraline> 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 <floraline> i have not been able to figure out what is causing this
21:34:25 <floraline> 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 <zalyar> ebering gammafunk silver rune isnt in my v:5
21:43:59 <zalyar> and... i reopened my game and its there
21:49:35 <floraline> this is the first i'm hearing of the lobby being slow, is it consistent?
21:50:11 <gammafunk> I haven't tried it much more than this one time
21:50:11 <gammafunk> just wanted to get a screenshot of the minimap
21:50:16 <gammafunk> I forget if I've tried to stream on twitch from cko, possibly not
21:50:26 <floraline> it's something like a 1 in 7 chance that a console game will not appear in webtiles when started
21:50:34 <gammafunk> interesting, I'll keep that in mind
21:50:42 <floraline> some failure related to the socket on disk that webtiles wants to read from
21:50:52 <gammafunk> yeah, one thing I noticed is that the reported idle time was over 30 minutes out of date
21:50:58 <gammafunk> it said I had been idle for 36 minutes
21:51:04 <floraline> yeah i think that's due to the same issue
21:51:07 <gammafunk> or something along those lines
21:51:13 <floraline> somehow it does know a game is going on but it has no info on it
21:52:31 <floraline> a webtiles PR might be able to hide this issue but it's frustrating to not know the root cause
21:55:49 <gammafunk> floraline: yeah, seems to be happening again now
21:55:52 <gammafunk> can you spectate me on cko?
21:56:00 <floraline> nope
21:56:05 <gammafunk> it seems to load the chat as I see the chat window + 2 spectators
21:56:09 <gammafunk> yet it stays at loading
21:56:17 <gammafunk> yeah, see you in chat as well
21:56:29 <gammafunk> and chat does work, weird
21:56:39 <gammafunk> yeah, see your message as well
21:57:00 <gammafunk> wonder if just reconnecting will get it to work eventually
21:57:14 <gammafunk> ah, indeed
21:57:23 <gammafunk> I saved in ssh and hit play again
21:57:26 <gammafunk> then I could spectate
21:57:44 <gammafunk> and it seems to spectate normally
21:57:45 <floraline> yep
21:57:56 <gammafunk> well at least I know that it can be made to work eventually, helpful if I try to stream
21:57:59 <floraline> i'm trying to find the line of code that fails, i found it before
21:58:07 <floraline> yeah it's an easy workaround thankfully
21:58:11 <floraline> but still super frustrating
21:58:30 <floraline> as far as i can tell, spectating from the console side works just fine
22:00:09 <floraline> 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 <floraline> during connect() in this same class
22:01:10 <gammafunk> yeah, that's just the very general method to send a json message
22:01:21 <gammafunk> it's more that we don't know the conditions that are causing failur
22:01:22 <gammafunk> e
22:01:35 <floraline> right
22:02:30 <floraline> i was thinking some better error handling there could queue it for a retry or something
22:22:10 <gammafunk> floraline: well, that's something that affects every single message sent, so you have to be careful about its behaviour
22:22:16 <gammafunk> it would be much better if we knew what exactly was happening
22:22:40 <gammafunk> 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_