PRs welcome

I actually did try but it's split into so many workflows I lost confidence.

Problem solved! Turns out I had a .wad in my Wii U's payfold loader.

Except for the spellchecker this LGTM (pulled, used, didn't crash) 👍

I love that spell check said "you should remove 'MRT'" and now says "hey, I don't know the word 'MRT'". 😡

Ah yes! The long-awaited moment when I'll have to support 5 ROS distributions at once.

This is why they pay you the big bucks!

@roydahan the rpm artifact tests are a joke, they fail more than they pass.

This condition should never be reached so we think it would make sense for a failure to occur if it did

If we prioritize fixing this test here is the reference for putting Humpty Dumpty back together again:

• https://github.com/kubernetes/test-infra/pull/36502

Was this entirely vibe coded?

Maybe I could just throw PNSE from the covertor if it's running on big-endian ? Or maybe I'm missing the point entirely

unsigned-fail-fork: test succeeded

Negative diffs are the best diffs

Please run more AI agents to help you to post here more digital garbage. 😂

@shajia-deshaw This will be fixed in v1.23.0 in 2026 Q2.

LRC works when “Think” is turned off and back on again. 🫥

I have no lungs but I must BREATHE

Potentially confusing variable names. Could there be anything clearer than

destinationDestination

this feature has been implemented. sorry for it taking three years!

lol fair. I always take compilation time as an excuse to go get a glass of water

Fixed by using 💰.

I will add a cognito tier condition. If it alerts, it should be a

(╯°□°)╯︵ ┻━┻

There is a reason it is not working…. The new Antigravity changed how UI is handled….

too much shitcode on your hands? solution:

[Obsolete("Use \"this\" instead.")]

This was also generated by

sphinx-quickstart

Considering the RP2350 support is still experimental, I'd propose to YOLO it and see if anything transpires afterwards.

Reviewed as best as I could for large workflow changes. Lets keep an eye out on the next release.

FYI @puneetlath in case the App deploy explodes

let's panic here for consistency. We'll replace it later on with proper goroutine error handline w channel

Why would anyone need to return a 418 error? (I should note that the current code doesn't even include "418" in its output.)

it's funny how they vibe code their own product and seem to work on production...

I would very much argue that stealing a car owned by the person you're meeting is absolutely not "behaving yourself" lol

But then stealing a random person's car is fair play by Yakuza standards? ^^

Why the hell did we wanted to do an elixir app btw? I don't even remember xD