Ayaz Salikhov

### Are you a maintainer? - [x] Yes, I am a maintainer

Waiting for https://github.com/mamba-org/mamba/issues/3741 to be enabled though

Fix: https://github.com/boostorg/fiber/issues/289 Clarify instructions for using AddressSanitizer with Boost.Context.

https://github.com/XRPLF/clio/actions/runs/20374531316/job/58552082833#step:8:3950

There are additional flags for Clang when running with UndefinedBehaviorSanitizer https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html > -fsanitize=undefined: All of the checks listed above other than float-divide-by-zero, unsigned-integer-overflow, implicit-conversion, local-bounds, vptr and the nullability-* group...

During the nightly pipeline we've got a failure like this: ``` [----------] 1 test from MigrationCassandraManagerObjectsTableTest [ RUN ] MigrationCassandraManagerObjectsTableTest.MigrateExampleObjectsMigrator munmap_chunk(): invalid pointer /__w/_temp/a769532f-87c6-44ae-84ed-be936f7d09a5.sh: line 2: 38 Aborted (core dumped)...

Now, we create it every time, which is not really useful. And most of failures because of CI runners being unstable. It would be great: - to only have one...

Update to latest boost release

1

The old one prevents us from enabling address sanitizer, as boost asio crashes

Fix flaky tests

1

Currently, some of our unit tests are flaky. There are 2 types I know of: 1. The ones are using `createLedgerHeader` Problematic code: https://github.com/XRPLF/clio/blob/develop/tests/common/util/TestObject.cpp#L83 In CI: https://github.com/XRPLF/clio/actions/runs/15022476202/job/42215720850 2. Sleep based...

https://github.com/XRPLF/clio/pull/2168#discussion_r2116094410