| --- Log opened Tue May 04 00:00:04 2021 |
| 01:11 | | Degi_ [Degi@Nightstar-008.mac.14.89.IP] has joined #code |
| 01:12 | | Degi [Degi@Nightstar-p0f.hns.4.77.IP] has quit [Operation timed out] |
| 01:12 | | Degi_ is now known as Degi |
| 01:16 | | KiMo|autorejoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code |
| 01:16 | | mode/#code [+o KiMo|autorejoin] by ChanServ |
| 01:17 | | Kindamoody[zZz] [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds] |
| 01:32 | | himi [sjjf@Nightstar-1drtbs.anu.edu.au] has joined #code |
| 01:32 | | mode/#code [+o himi] by ChanServ |
| 02:28 | | Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed] |
| 02:57 | | ErikMesoy [Bruker@Nightstar-ptnpo0.bb.online.no] has quit [Ping timeout: 121 seconds] |
| 03:14 | | ErikMesoy [Bruker@Nightstar-hvevn5.bb.online.no] has joined #code |
| 05:22 | | Vorntastic [uid293981@Nightstar-h2b233.irccloud.com] has joined #code |
| 05:22 | | mode/#code [+qo Vorntastic Vorntastic] by ChanServ |
| 05:24 | | VirusJTG [VirusJTG@Nightstar-799.99q.104.208.IP] has quit [Connection closed] |
| 07:09 | | KiMo|autorejoin is now known as Kindamoody |
| 07:17 | | celticminstrel [celticminst@Nightstar-pg1f6i.dsl.bell.ca] has quit [Ping timeout: 121 seconds] |
| 07:20 | | celticminstrel [celticminst@Nightstar-h2dpj8.dsl.bell.ca] has joined #code |
| 07:20 | | mode/#code [+o celticminstrel] by ChanServ |
| 07:24 | | himi [sjjf@Nightstar-1drtbs.anu.edu.au] has quit [Ping timeout: 121 seconds] |
| 07:30 | | macdjord [macdjord@Nightstar-re5.7if.45.45.IP] has joined #code |
| 07:30 | | mode/#code [+o macdjord] by ChanServ |
| 08:02 | | mode/#code [+o ErikMesoy] by ChanServ |
| 09:29 | | abudhabi [abudhabi@Nightstar-6ei8vq.adsl.tpnet.pl] has joined #code |
| 09:32 | | abudhabi_ [abudhabi@Nightstar-lrn3vr.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds] |
| 10:05 | | catalyst_ [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code |
| 10:05 | | catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Connection reset by peer] |
| 11:08 | <@gnolam> | Mmm, API documentation... in Japanese. |
| 11:13 | < catalyst_> | tasty |
| 11:13 | | catalyst_ is now known as catalyst |
| 12:46 | | McMartin [mcmartin@Nightstar-i80eaa.ca.comcast.net] has quit [Operation timed out] |
| 12:47 | | McMartin [mcmartin@Nightstar-i80eaa.ca.comcast.net] has joined #code |
| 12:47 | | mode/#code [+ao McMartin McMartin] by ChanServ |
| 14:15 | <&ToxicFrog> | So last night I implemented the Stab spell |
| 14:15 | <&ToxicFrog> | And upon testing, every time one wizard stabs another, the world stops existing |
| 14:15 | <&ToxicFrog> | so I've done something wrong there |
| 14:18 | <@TheWatcher> | Or very, very right~ |
| 14:39 | <@celticminstrel> | XD |
| 14:43 | <@ErikMesoy> | My baseless speculation from seeing none of your code and only general bug habits is that perhaps the Stab spell works this way because stabbing completes a spell at the same time as it starts the same spell, causing internal state confusion about whether the spell is finished yet. |
| 14:43 | <@ErikMesoy> | Am I anywhere near correct? |
| 14:46 | <&ToxicFrog> | Not even close. |
| 14:46 | <&ToxicFrog> | The bug was actually in Shield, but due to the way I constructed the test case it manifested immediately after the log message for Stab. |
| 14:47 | <&ToxicFrog> | And the root cause was that Shield's finalizer had handlers for when it was countered or dispelled, but not when it succeeded (because it succeeding is a no-op; all the important parts happen before finalization), and I forgot to make "no success finalizer" eqv to `identity` |
| 14:47 | <&ToxicFrog> | So instead it implicitly got a success finalizer that deleted the world |
| 14:48 | <@celticminstrel> | Why would that be the impllicit action!? |
| 14:49 | <&ToxicFrog> | celticminstrel: because the finalizer has the signature (World SpellEffect -> World) and with no matching (cond) case it evaluated to nil |
| 14:49 | <&ToxicFrog> | Lessons learned here include "make it impossible to write finalizers that aren't correctly type-annotated", because that would have caught this instantly. |
| 15:00 | | Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code |
| 15:00 | | mode/#code [+qo Vornicus Vornicus] by ChanServ |
| 15:07 | <@sshine> | does anyone here use Terraform? I'm using it with AWS at work, and now I started to use it privately with DigitalOcean. I think it's pretty neat. :) |
| 15:22 | | Vorntastic [uid293981@Nightstar-h2b233.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity] |
| 17:20 | | Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has joined #code |
| --- Log closed Tue May 04 19:10:42 2021 |
| --- Log opened Tue May 04 19:11:37 2021 |
| 19:11 | | TheWatcher [chris@GlobalOperator.Nightstar.Net] has joined #code |
| 19:11 | | Irssi: #code: Total of 30 nicks [18 ops, 0 halfops, 0 voices, 12 normal] |
| 19:11 | | mode/#code [+o TheWatcher] by ChanServ |
| 19:11 | | Irssi: Join to #code was synced in 14 secs |
| 22:49 | | Kindamoody is now known as Kindamoody[zZz] |
| 22:52 | <&jeroud> | sshine: Oh gods, terraform. |
| 22:53 | <&jeroud> | It's no longer the worst tool I've ever chosen to use, but only because it's improved slightly over the past few years and the k8s ecosystem is full of such utter garbage. |
| 22:53 | <&jeroud> | That said, if you're not doing anything complicated it's pretty good. |
| 22:54 | <&jeroud> | And despite the significant effort I've put into looking, I have yet to find anything that even comes close. |
| 23:03 | <&jeroud> | The main thing to watch out for these days is unfortunate ordering (some APIs report success before the thing they're doing is actually ready, sometimes dependencies need to be listed explicitly, etc.) but *usually* in those cases a second `apply` will succeed. |
| 23:05 | <&jeroud> | Far more annoying, but only relevant if you regularly destroy the things you provision (which we do a lot for test environments), is that "nested" resources can be orphaned and require manual state manipulation to fix. |
| 23:10 | <&jeroud> | For example, we create an EKS cluster and also manage auth maps within that cluster in the same terraform module. When we tear down the environment, it's possible for the EKS cluster to be destroyed before the things inside it. This means the auth maps are gone (because the k8s they lived in is gone) but tf still thinks they exist because there's no way to talk to the now-gone cluster to get any information or perform any actions. |
| 23:18 | <&jeroud> | Anyway, enough about the bad stuff. Terraform is absolutely worth using just for the ability to version-control what your infrastructure's supposed to look like. Everything else is just a bonus on top of that. :-) |
| 23:23 | | Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has quit [Ping timeout: 121 seconds] |
| --- Log closed Wed May 05 00:00:30 2021 |