Tyler Neely

This needs to be performed in a different way than how our current failpoints are being handled, as when a failpoint is triggered, all writes from that point onward until...

after #1095, we're at this memory usage before employing swizzling 

One option I'm considering is to have write operations fail with an error that clearly specifies that subscribers are not keeping up. Because the reservation happens before any modifications actually...

Similar to #1165 I see that issue being addressable by having the `Event::Batch` that is sent to subscribers.

@fernandobatels hey! if you are actually seeing corruption, this is a bug, but it's not clear that anything is being corrupted. It seems like your real issue is that sled...

Hi @fernandobatels, I just cut sled version 0.31 which I think might somewhat improve your recovery times. I would be quite curious to know if your issue is addressed, or...

Thanks for the info! There are 2 things I want to improve as patch updates to 0.31, which have to do with garbage collection and using multiple threads to create...

https://camshaft.github.io/bolero/features/input-shrinking.html looks really cool, thanks for the tip!

I would like this change eventually. Historically I've tended to bump the MSRV pretty conservatively after feeling kind of swamped by people telling me things were broken after I cut...

@Kerollmops yeah! I was thinking this could also work for things like `auto_increment`, `unique`, `foreign_key(other_table.column)` that can be set on individual members.