Me: Is flatulence inherently denser than air? Assuming a person has a large volume of gas inside their body, would they lose weight after releasing all of it?
Gemini:
Just for recording:
`sudo security authorizationdb reset https://t.co/oiVHYCQXzY.backupd` can fix the `Backup failed: BACKUP_FAILED_DEVICE_LOCKED (80)` error of time machine.
We lispers don't want you to know, but Common Lisp, Scheme, Clojure, Picoisp, Emacs Lisp, Hy, Arc, Bel, Carp, Fennel, NewLisp, Shen, Janet, Ferret, Satori, Gerbil, Racket are not difficult if you know LISP 1.5, quite similar in syntax
China’s is seeing unprecedented money supply growth:
China's M2 money supply is up to a record ~240% of GDP, the highest among any major economy in the world.
This metric has surged +100 percentage points since the 2008 Financial Crisis.
Over this period, China’s M2 money supply has surged +500% in Dollar terms.
By comparison, the country's gold reserves and total FX reserves have risen +100% and +60%, respectively.
To put this into perspective, Japan's M2-to-GDP ratio, the next highest, stands at ~185%, while the US sits at ~70%.
China's monetary expansion is unlike anything seen among major economies.
Cloudflare spent 6 weeks chasing a bug in the hyper Rust HTTP library. The fix was 4 lines. 🦀
The symptom: image responses returning HTTP 200 but with truncated data : a 14.9 MB response arriving as 219 KB, no errors logged anywhere.
The root cause: a single `let _ =` in hyper's dispatch loop discarding a `Poll::Pending` signal from the flush operation. The socket buffer filled up, flush returned pending, but hyper ignored it and called shutdown anyway, dropping the remaining data silently.
What made it so hard to find:
→ Only happened in production, never with curl
→ Only triggered for large images under real concurrency
→ Disappeared when strace was broadened (slowed things just enough to shift timing)
→ All application-level logs reported success
The breakthrough came from strace : kernel-level syscall tracing, which showed shutdown being called after just one write, with 14.8 MB still in the buffer.
The bug existed in hyper across multiple major versions (0.14 through 1.8). It was invisible because most readers drain data fast enough that the socket buffer never fills. A new, faster intermediary introduced just enough backpressure to expose it.
Fix is now merged upstream in hyperium/hyper PR #4018.
A masterclass in debugging async Rust at the systems level.
🔗 https://t.co/yd3RY2mfOf
#RustLang #AsyncRust #Hyper #SystemsProgramming #Debugging #OpenSource #Cloudflare