Angelo Bulfone

Related issue: https://github.com/rt64/rt64/issues/19

> > Related issue: [rt64/rt64#19](https://github.com/rt64/rt64/issues/19) > > boom shroom does this PR work for you as well? I don't currently have this exact patch, but I do have the same...

> Forcing an unsupported backend will end up in a crash. I'm not sure what you are expecting. What I was expecting was setting a _preferred_ backend, and then a...

If you know you're going to be having back-pointers, I suggest taking a look at std::rc::Weak. Weak pointers allow access to a reference counted object without forcing it to stay...

Complication: Zed downloads its own prebuilt binary of NodeJS (currently `18.15.0`; closest version in nixpkgs is `18.20.2`). While less of an issue for MacOS or other Linux distros that have...

Since background_compression happens, well, in the background, it's not as important for it to be fast and it makes sense to let the system use spare background cycles getting the...

I don't have the spinning CPU, but I can report on copygc reading without writing, and rebalance in a perpetual disk sleep. I'm interested in seeing if 6.8-rc1 has any...

More potentially useful diagnostics: `internal/moving_ctxts`. `bch-rebalance` is clearly deadlocked waiting on a closure that seems to never finish. ``` 🠪 cat /sys/fs/bcachefs/4d4903de-99c8-41a1-ab6a-83431f05b0dc/internal/moving_ctxts rebalance_work: data type=user pos=reflink:0:5385176:0 keys moved: 1 keys...

Mounting the filesystem in question as a fusermount didn't show the same problem and letting the daemons run for a bit even seems to have fixed it when remounting in...

`Iterator::sum` takes `self` by value. It shouldn't be possible for the caller to tell if every element was consumed or not without side effects happening from the iteration. If you...