First part of a new long term home project coming in. An #Ubiquiti PoE+ switch to power a small #Kubernetes cluster built using #raspberrypi nodes. Going to blog about every step once it has been completed. But it is going to be a few quarters long project doing bit by bit
@wyri Thanks for putting that together, @lcobucci! This is pretty much exactly what I meant when I wrote “…when I've needed a spy I usually end up implementing it directly in the code.”
For all intents and purposes, I’d call this a spy. It’s sole purpose is to fulfill a contract and record how it’s called. I’ve occasionally shipped spy implementations alongside contracts to facilitate testing, but they usually end up in a Testing\ sub-namespace.
@beausimensen@lcobucci Yup that's exactly what I needed in this situation, a spy, a way to look into it to know if expected calls were made and not care about the rest.
Thinking back, over the years, I probably need a spy most of the time and ended up adding mock calls that I didn't needed/cared for.
As I'm importing my cloud #Kubernetes cluster into #Terraform I want to look at a new ingress. Looking for something very lightweight, runs on both ARM64 and AMD64 so it can run on my cloud and home clusters for simpler management, and is easy to manage (the less work the better). What is everyone using?
Let me partially rewrite this #PHP package I thought, how hard can it be? Yup now I'm learning all about the small details and timings of the protocol the package implements 😅 .
Found one minor mistake and it runs great now. Time to update all the examples, and test all of them. Run the test suite and see how much of it has broken. But it runs:
@ramsey@arnan@wyri It would have been better to restart the project, re-using bits that were usable. But the majority feared the work and voted against it. So now instead of working on something better, they spend time patching and fixing legacy crap code...
@syntaxseed Aye, this was from the @reactphp call where we looked at usage statistics and realised that promise v2 came out so quickly after promise v1 that v1 barely got any usage. It got more users on HHVM then on 5.x 😂
Rethinking configuration for my #OpenAPI/#OAS#PHP client generator while transforming it into a package generator. Currently using #YAML hydrating into #PHP classes. Mainly looking to support both those wanting to keep it simple and those with complex setups without to much duplication.
Been working on this slowly over the past few days and honestly #PHP is the way to go. Other formats are nice, but #PHP allows for so much flexibility 💗 !
Alright new toy/project came in today. The Everything Presence One by #EverySmartHome. It's up and connected to the #WiFi , #esphome pod is up and running, now to connect #homeassistant to it and the experimenting begins!
The EPO is in its final place! Still fiddling a bit with the mmWave sensor to only trigger when desired. But that also means slightly reaiming them a bit. Going to take the time of day and the amount of light into account as well. So it that it only turns on when there isn't a lot of light, or not to bright in the middle of the night unless we overrule it.
Run your own #kubernetes cluster on #raspberrypi's they said, it will be fun they said. So now once every blue moon there is a leader change in the middle of a #terraform apply 🤣
@ninoles Looking forward to that. And cloud companies are working hard on that. Just don't run into weirdly documented issues edge cases because then all of this suddenly start to matter again 🤦♂️
Took a couple of weeks but it's reliably running locally on my laptop. At higher throughput than some years ago on dedicated hardware, before the refactoring 😎 .
@wyri (There should also be a 1.0 release at some point, I guess. But that might be just me. 😅 I think Bunny is heavily used in production, and SemVer says that 0.* interfaces are allowed to change at any time.)
@merms No need to apologise for prioritising your newborn over replying. Congratulations 🎉 ! And yes there should be a 1.0 release. Doing the merging of both clients is a bit box to tick off for that.
And yes you're right, it had its own event loop in the sync client. Kinda forgot about that after yanking it out 😅 .
To bad you can't help me test 0.6 before tagging it outside my own set up for it. But thanks for the context on it.
Just a FYI but if your cookie wall starts with "We value your privacy" and then forces me to go through a list of 1512 partners to turn them off one by one, instead of an easy "Reject all" next to your "Accept all". You don't give a flying fuck about my #privacy.
@anthony@brunty Yup, could be geo. But tried on desktop and either my auto-fuckoff fix it for me, or unlock blocks it, or it doesn't show there. And yes I'm using Chrome on Android.
@50gp@brunty@anthony Ok sure, I'm using Pi-Hole as a network wide adblocker but that doesn't catch it. How would you install an adblock extension on Chrome on Android?
Really appreciate how #untappd is handling the first bit of communication when the app can't reach their API. One of my pet peeves for years is that errors blame the users' internet connection instead of the actual problem. (Which can still be the users' connection.)