Pat

The DCO failure is a hard block

Can you submit a docs PR to revert it? I can merge that, Github doesn't want to auto-revert probably because it was quite a while ago.

I would not be a fan of changing it from one hardcoded value to another, let's make it configurable with a default.

> Hi [@patrick-stephens](https://github.com/patrick-stephens), I suspect this issue is no longer relevant given how it's been more than 2 years, but are you by any chance still suffering from the same...

Thanks for this @ccampo133 , could you just ensure your commits are signed and follow the contribution guidelines for the commit message?

We'll need a valgrind report as well to ensure no leaks.

Ignore the appveyor failure due to a flaky test - this is fixed on latest `master` I believe as well.

Can you step up to the latest version (3.0.0) and confirm it still happens there?

Sure, it just needs someone to submit the PR to do it. Have a look at the packaging directory, we use a containerised build process for everything and there is...

We should probably add Rocky Linux and Centos stream 10 support too.