djg

Could you include a before/after benchmark for this?

## 0.16.0 ### Zero-amount transfers Zero-amount transfers are now permitted. This is a _breaking API change_ which is gated in the state machine by the _client's_ release. As of `0.16.0`:...

The tree fuzzer found this failing seed, which taught me something interesting about space amplification for trees with random key updates!: ``` zig build -Drelease fuzz -- lsm_tree 4088940554726182876 ```...

Temporarily pausing this to give https://github.com/tigerbeetle/tigerbeetle/pull/2544 more fuzzer cycles.

I have no objections -- that would be more convenient than going through `scripts`! I just wasn't sure whether it warranted increasing the size of our binary. It would be...

> Let's add a smoke test to our integration_tests here. :+1: > I think we can tack it onto the end of benchmark smoke test, to minimize the runtime. It'll...

re: upgrade instructions -- we should recommend that the source and the destination binaries already be on the same filesystem before the `mv tigerbeetle /usr/bin/tigerbeetle`, to ensure that it is...

(Out of scope for this PR, but...) > re: upgrade instructions -- we should recommend that the source and the destination binaries already be on the same filesystem before the...

> this doesn't work when clients spawn a TigerBeetle process themselves We are inconsistent about who is responsible for setting up TB. i.e. the node tests (iirc) are handled by...

Hi @sandeepanumula8690, TigerBeetle depends on Zig 0.11.0, not 0.12.0 ([yet](https://github.com/tigerbeetle/tigerbeetle/pull/1878)) -- they are not compatible.