Having to recycle your #kubernetes nodes because the #HPA isn't scaling up your #Mastodon#sidekiq so you're now lagging 15K jobs behind looks like this in the #UI:
Ok ok I admit that I recycled my nodes because I could. Kicking the pod probably also would have fixed it but they where up for 82 days and it felt fun
Had fun this weekend working on a performance focussed proof of concept using Bunny in the #PHP#queue interop contracts. The first metrics are in using the #RabbitMQ cluster on my #Raspberrypi#Kubernetes home cluster. (Which isn't meant for high performance. Still pleased by these numbers.)
Thanks to @jay Bunny #PHP will support client properties in the upcoming 0.5.6 and 0.6 releases. Client properties can be used to set a human readable name to your connection with #RabbitMQ:
Doing some #PHP package maintenance tonight, this dev dependency bump kinda stood out 😅 . Mainly I make sure my packages work on the latest #PHP versions, either through support requests or when I run into issues myself. Most of my packages are designed with the future in mind.
The long-term plan is to get reusable workflows for every package and #Renovate to open PR's more aggressively than #dDpendabot to uncover potential future issues. Currently rolling that out with every package I
Merged https://github.com/jakubkulhan/bunny/pull/147 earlier today into the 0.6 dev branch. You can test it out with composer require bunny/bunny:^0.6@dev. Looking forward to any feedback on it before releasing bunny/bunny 0.6 in a few months. With the following other changes:
Kinda forgot how much fun it was to write code stitching map tiles together, and also how easy it was. Currently at 82 lines of #PHP. Once finished it will be a new package, as the #golang has some massive glaring bug in it that took me 6 years to find. Sprinkling some threads and #AMQP over this once it's done. The home clusters fans will sing once more
Another reason to run things such as #RabbitMQ as a cluster: If the #Docker image is missing the #arm64 arch one pod will stay pending while the continues working
Honestly, #GitHub could use a report spam feature in the UI instead of opening a ticket. Getting tagged in random issues hijacked with posts of crypto scams is getting ridiculous at this point.
Been putting the finishing touches on Bunny's transformation into #fibers PR. One of the major things for me there is visualizing the changes, especially the breaking changes. For example switching from a promise based API to a fibers based API:
Great, really should have a look at #chainguard based #Docker images: JavaScript Actions in Alpine containers are only supported on x64 Linux runners. Detected Linux Arm64