ASuciuX

@jcnelson @kantai From the benchmarking results, the implementation with `faster-hex` is better, but also it adds an extra dependency. Please let me know if you think this is worth adding.

> Per the call today, I think we should defer further consideration of this until we remove hex encode/decode from the DB I/O paths (since that's where a lot of...

Awesome, looks good!

Hello, would this be possible on the txt files alone or would it require the jsons? Or would it be another mechanism to track these?

Our existing workflow consists of two phases: Logging and Tracking. **Tracking Phase** In the Tracking phase, the process unfolds as follows: - Upon the opening of a pull request or...

I intended to ask for an implementation of running `cargo nextest` instead of `cargo test` as well. So, I think that would be really useful. Also, it is used on...

> > 3. https://github.com/ASuciuX/stacks-core/actions/runs/7901429286?pr=57 > > it looks like this build failed on `4: unmutated build failed` - should this be expected to pass? Thanks for pointing that, it shouldn't...

This is the workflow that was run before. Now it is running as expected, without stacks-signer, even though there are changes on that package. https://github.com/ASuciuX/stacks-core/actions/runs/8009445597/job/21878164232?pr=59

Yes, there are unviable mutants in this run. If it returns unviable, it means it finished the workflow as the problem was keeping the run till the whole github workflow...

[Benchmark Reference](https://github.com/ASuciuX/benchmark-rust/blob/master/benches/results.md) showcasing the increase performance of `for_loop_iter` with `append` instead of `map` and `flat_map` related to https://github.com/stacks-network/stacks-core/pull/4425/commits/fe4be97ad3911370916620cd3ecefd222535c8a6 .