ChanServ changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things Sandstorm and Cap'n Proto. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev | Channel logs available at https://libera.irclog.whitequark.org/sandstorm
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #sandstorm
xet7 has quit [Remote host closed the connection]
xet7 has joined #sandstorm
TC01 has quit [Ping timeout: 250 seconds]
TC01 has joined #sandstorm
kentonv has joined #sandstorm
<kentonv> oh geez, so many PRs ready for review and bad timing as I just moved and won't be able to review anything this weekend.
<ocdtrekkie> Moved? House done?
<kentonv> no, sadly, that's going to take another 18 months
<kentonv> so this was my... second-to-last move, I suppose
<ocdtrekkie> Thought it seemed a bit soon. I'm looking forward to the kentonshouse.com overhaul.
<kentonv> we had to get out of the apartment. It was just so annoying having to mask up to go down the elevator. Plus we're having another kid in December and there wasn't going to be space. So we rented a house.
<kentonv> I'll do an extra release this month, maybe next weekend, to pick up some of the PRs that need a more careful look
<kentonv> (had to anyway since otherwise the next release date would fall on monthly WAN party day...)
<kentonv> something, somewhere in Meteor is trying to auto-create an index on users.services.oidc.id with different settings than the index we already have and so it fails and the server crashes on startup
<kentonv> oh I see, it has always been this way, but Meteor 2.4 changed the MongoDB driver such that this is now an error, rather than the extra index creation being ignored
<kentonv> omg, the Node Mongo driver doesn't apparently support dropping indexes?
<kentonv> oh, no, it's just Meteor's wrapper doesn't expose it
<kentonv> oh great, selenium is broken again
* isd groans
<isd> broken how?
<kentonv> I wish I knew. `java.lang.IllegalStateException: size = 2`
<kentonv> what could it mean? Who knows?
<kentonv> it's openjdk 17
<kentonv> openjdk 17 just does not work
<kentonv> this is the second java program I've tried to run with openjdk 17, and the second time it has just failed in random ways, and switching back to openjdk 11 fixes everything
<kentonv> (Debian has packages for openjdk 17 and openjdk 11)
<kentonv> however, I now see 19 assertion failures where I had 3 at the last release
<isd> Yay?
<isd> I assume there's is some change upstream of us that has only now reached Debian
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #sandstorm
<isd> The extra failures are all problems with the meteor test app failing to launch; they cropped up for me and in CI in time for last release.
<isd> ...and I was able to reproduce them locally on older revisions that used to work, and unable to reproduce them in a bullseye VM at the time.
<kentonv> is this log spam also related: "Unhandled exception in Promise: [Error: remote exception: stream disconnected prematurely]"
<isd> I don't know if it's related. I had noticed there seems to be more of it than there used to be.