Use tikv jemalloc fork

[jackkleeman]

As otherwise the commit doesn't reliably download on new checkout. This commit is only tagged in the tikv fork, and Github seems keen on GCing it from the original repo.

[BusyJay]

As otherwise the commit doesn't reliably download on new checkout.

What exact problems did you meet? Seems all tests run well.

[jackkleeman]

[builder 1/3] RUN just arch=amd64 libc=gnu chef-cook --release --bin restate-server
#15 0.167 cargo chef cook --recipe-path recipe.json   --release --bin restate-server
#15 0.965     Updating git repository `[https://github.com/restatedev/aws-sdk-rust`](https://github.com/restatedev/aws-sdk-rust%60)
#15 2.341     Updating crates.io index
#15 2.398     Updating git repository `[https://github.com/restatedev/jemallocator`](https://github.com/restatedev/jemallocator%60)
#15 3.178     Updating git submodule `[https://github.com/jemalloc/jemalloc`](https://github.com/jemalloc/jemalloc%60)
#15 5.581 error: failed to get `tikv-jemallocator` as a dependency of package `restate-server v0.0.1 (/restate/server)`
#15 5.581 
#15 5.581 Caused by:
#15 5.581   failed to load source for dependency `tikv-jemallocator`
#15 5.581 
#15 5.581 Caused by:
#15 5.581   Unable to update https://github.com/restatedev/jemallocator?rev=f7adfca5aff272b43fd3ad896252b57fbbd9c72a#f7adfca5
#15 5.581 
#15 5.581 Caused by:
#15 5.581   failed to update submodule `jemalloc-sys/jemalloc`
#15 5.581 
#15 5.581 Caused by:
#15 5.581   object not found - no match for id (e13ca993e8ccb9ba9847cc330696e02839f328f7); class=Odb (9); code=NotFound (-3)
#15 5.585 thread 'main' panicked at /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-chef-0.1.62/src/recipe.rs:204:27:
#15 5.585 Exited with status code: 101
#15 5.585 stack backtrace:
#15 5.590    0: rust_begin_unwind
#15 5.590              at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:645:5
#15 5.590    1: core::panicking::panic_fmt
#15 5.590              at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/panicking.rs:72:14
#15 5.590    2: chef::recipe::Recipe::cook
#15 5.591    3: cargo_chef::main
#15 5.591 note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
#15 5.592 error: Recipe `chef-cook` failed on line 90 with exit code 101
#15 ERROR: process "/bin/sh -c just arch=$TARGETARCH libc=gnu chef-cook --release --bin restate-server" did not complete successfully: exit code: 101

[jackkleeman]

Its sporadic, doesn't happen every time but certainly appears to be about git GC - the commit isn't in a branch or tag on that repo so its not guaranteed present I think?

[BusyJay]

I see, thanks!