code logs -> 2021 -> Thu, 04 Feb 2021< code.20210203.log - code.20210205.log >
--- Log opened Thu Feb 04 00:00:24 2021
00:10 gnolam [lenin@Nightstar-ik80lk.priv.bahnhof.se] has quit [Connection reset by peer]
00:10 gnolam [lenin@Nightstar-ik80lk.priv.bahnhof.se] has joined #code
00:10 mode/#code [+o gnolam] by ChanServ
--- Log closed Thu Feb 04 00:38:31 2021
--- Log opened Thu Feb 04 00:38:37 2021
00:38 TheWatcher [chris@GlobalOperator.Nightstar.Net] has joined #code
00:38 Irssi: #code: Total of 26 nicks [16 ops, 0 halfops, 0 voices, 10 normal]
00:38 mode/#code [+o TheWatcher] by ChanServ
00:38 Irssi: Join to #code was synced in 16 secs
00:40 Reiver [quassel@Nightstar-ksqup0.co.uk] has joined #code
00:40 mode/#code [+ao Reiver Reiver] by ChanServ
00:40 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [[NS] Quit: -a- Connection Timed Out]
00:40 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
02:06 bluefoxx [fuzzylombax@Nightstar-gmbj85.vs.shawcable.net] has joined #code
03:29 Degi [Degi@Nightstar-t8ci2j.pool.telefonica.de] has quit [Operation timed out]
03:33 Degi [Degi@Nightstar-mn9qcv.pool.telefonica.de] has joined #code
04:34 VirusJTG__ [VirusJTG@Nightstar-42s.jso.104.208.IP] has quit [Connection closed]
04:35 VirusJTG__ [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code
05:44 celticminstrel [celticminst@Nightstar-46hkr3.dsl.bell.ca] has quit [[NS] Quit: And lo! The computer falls into a deep sleep, to awake again some other day!]
07:11 abudhabi [abudhabi@Nightstar-55l8kt.adsl.tpnet.pl] has joined #code
09:31 crystalclaw [crystalclaw@Nightstar-12q9ui.xyz] has quit [Ping timeout: 121 seconds]
09:31 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
09:31 mode/#code [+qo Vornicus Vornicus] by ChanServ
09:34 NSGuest52444 [crystalclaw@Nightstar-12q9ui.xyz] has joined #code
09:38 NSGuest52444 [crystalclaw@Nightstar-12q9ui.xyz] has quit [Operation timed out]
11:19 Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has joined #code
11:26 catalyst_ [catalyst@Nightstar-8qmm32.dab.02.net] has joined #code
11:28 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Ping timeout: 121 seconds]
11:57 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
12:00 catalyst_ [catalyst@Nightstar-8qmm32.dab.02.net] has quit [Ping timeout: 121 seconds]
13:23
<@sshine>
today: fixing PHPUnit tests on an expired PhpStorm (IDE) that closes every 30 minutes, on a MacBook Air that randomly disconnects me from the interwebs every 2 hours.
13:24
<@sshine>
upside: I learn which unit tests secretly connect to the internet when they're not supposed to, so I get to mark them as problematic. and I somehow work harder when I know that I have to restart the IDE sooner.
13:24
<@sshine>
I don't know what I saw in all this FOSS when shareware on legacy hardware provides this kind of user experience!
13:25
<@sshine>
re-running the test suite so many times and gradually marking test units to skip also taught me that the test order is non-deterministic.
13:34
<&ToxicFrog>
ND test order is pretty common (lots of test harnesess will run the tests in parallel if they can, for example) and even desireable (since it's more likely to expose issues where one test has an implicit dependency on state left lying around by a different test, which *shouldn't* be possible in principle but sometimes is)
13:35
< catalyst>
aye, many test frameworks will deliberately change the order each run
13:38
<@TheWatcher>
Uh, _why_ are you doing that to yourself?
13:57
<@sshine>
TheWatcher, I joined a company with a test suite that is best described as an overgrown backyard with rusty refridgerators, half tractors and wild animal nests. I decided to clean it up, because I need to run unit tests before I feel comfortable merging something. :-D nobody is challenging me, and it feels kinda nice.
13:58
<@sshine>
once the 4-5 fatal errors were removed, it had a 31% success for 600 tests. what's amazing here is that the number 31% is consistent. so no wildly non-deterministic tests detected yet!
13:58
<@TheWatcher>
I think that test suite describes most company test suites~
13:59
<@sshine>
my old employer had 50k tests running in parallel on a cluster so it took 5 minutes.
13:59
<@TheWatcher>
But I'm more wondering why you're using an expired phpstorm on a flakey macbook air, rather than... any alternative?
14:00
<@sshine>
TheWatcher, the flakey macbook air: I was promised a MacBook Pro with an M1 that arrives on Monday, and I gladly accepted this crap machine if I can skip from i7 to M1 straight away :)
14:01
<@sshine>
I didn't know this one had an i5 and too little RAM, though. right now I join the daily standup from my phone because, you know, connecting a screen, your earphones and going online is... a resource-intensive process!
14:01
<@TheWatcher>
-_-
14:03
<@sshine>
the expired PhpStorm: the team I'm working on was just acquired by the larger company, and I'm the first hire after the merger. they come from "let's just crack it" and the buying company is "we'll buy what you wanna use" -- and I don't want to use PhpStorm (which is a modified IntelliJ). I prefer VSCode. so today was the first day it expired, and I'm going to set up VSCode with devcontainers so that the
14:03
<@sshine>
Docker environment can run from there instead of inside PhpStorm. so while I'm working on the unit test suite, PhpStorm has better test integration, and on the side, I'm working on a similarly adequate setup with VSCode.
14:05
<@sshine>
apparently the PHP community is a little behind on setting up these things, so PhpStorm is unrivalled in that it can actually run PHPUnit inside Docker, export the whatever-XML-format test results, and apply them to the IDE testing UI (you know, the thing that provides a little icon next to each unit test based on whether it succeeded or failed). I have not tried to do that in VSCode, and I doubt it's
14:05
<@sshine>
advanced as far.
14:06
<@sshine>
I normally just run tests in the terminal.
14:07
<@sshine>
IntelliJ is awesome but sooo slow. I think that's generally what people don't like about Visual Studio. with a beefy enough computer, I don't experience that in Visual Studio. but I do experience it in IntelliJ. it just isn't fast.
14:07
<@sshine>
I just don't have any tolerance for latency in my own tools.
14:14 celticminstrel [celticminst@Nightstar-46hkr3.dsl.bell.ca] has joined #code
14:14 mode/#code [+o celticminstrel] by ChanServ
14:14
<@TheWatcher>
Yeah, IntelliJ has... definite speed issues IME too.
14:16
<@sshine>
VSCode, however, is blazing. and they seem to have good "project/workspace" support for arbitrary language environments.
14:17
<@sshine>
so, say, boot it up with Haskell and even without specialized plugins, the experience is good. and then in some cases, it goes up one, two or three notches.
14:18
<@sshine>
I used Vim 1997-2012, Emacs 2012-2020, and VSCode 2020-now :) I still use Vim a lot, though.
14:30 catalyst_ [catalyst@Nightstar-8qmm32.dab.02.net] has joined #code
14:32 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Ping timeout: 121 seconds]
14:53 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
14:54 catalyst_ [catalyst@Nightstar-8qmm32.dab.02.net] has quit [Ping timeout: 121 seconds]
17:25 abudhabi [abudhabi@Nightstar-55l8kt.adsl.tpnet.pl] has quit [NickServ (RECOVER command used by abudhabi_)]
17:25 abudhabi [abudhabi@Nightstar-abqipu.adsl.tpnet.pl] has joined #code
17:39 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Connection reset by peer]
17:39 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
17:41 ErikMesoy1 is now known as ErikMesoy
17:43 mode/#code [+o ErikMesoy] by ChanServ
18:01 Kindamoody[zZz] is now known as Kindamoody
19:17
<@sshine>
since PHPUnit doesn't have a @skip (it does have $this->markTestSkipped()), I've marked broken tests temporarily skipped by writing
19:17
<@sshine>
@requires PHP > 9000
19:17
<@sshine>
which is a Dragon Ball Z reference that my closest boss actually gets :-D https://www.google.com/search?q=more+than+9000
19:20
<@sshine>
https://www.youtube.com/watch?v=SiMHTK15Pik
19:25
< abudhabi>
The Y9k problem.
19:35
<@sshine>
yeah, this code will be redundant when PHP 9000.0 releases. they're at 8.0 now, though, so I hope we'll have migrated since.
19:57 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has joined #code
19:57 mode/#code [+o Reiv] by ChanServ
19:58
< abudhabi>
sshine, at end of life, signs up for cryonics. Unexpectedly, wake-up happens in the year 9000. "Why have I been revived now?" "It's the year 9000 and you know PHP."
19:59
<&McMartin>
9000 will be the next version just for spite
20:00
< abudhabi>
Nah, it'll just be some quirk of PHP 9 to evaluate that @requires statement as true.
20:01 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has quit [[NS] Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
20:01
<&McMartin>
Numeric comparisons now compare against all prefixes as well
20:01 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has joined #code
20:01 mode/#code [+o Reiv] by ChanServ
21:15 Kindamoody is now known as Kindamoody[zZz]
21:33 himi [sjjf@Nightstar-v37cpe.internode.on.net] has quit [Ping timeout: 121 seconds]
22:00 himi [sjjf@Nightstar-v37cpe.internode.on.net] has joined #code
22:01 mode/#code [+o himi] by ChanServ
22:12 abudhabi [abudhabi@Nightstar-abqipu.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds]
22:29 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
23:05 himi [sjjf@Nightstar-v37cpe.internode.on.net] has quit [Ping timeout: 121 seconds]
23:06 himi [sjjf@Nightstar-v37cpe.internode.on.net] has joined #code
23:06 mode/#code [+o himi] by ChanServ
23:21 Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has quit [Ping timeout: 121 seconds]
23:48 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has quit [[NS] Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
23:52 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has joined #code
23:52 mode/#code [+o Reiv] by ChanServ
--- Log closed Fri Feb 05 00:00:25 2021
code logs -> 2021 -> Thu, 04 Feb 2021< code.20210203.log - code.20210205.log >

[ Latest log file ]