Our current plan is to ship nanobind with resource leak warnings disabled (see https://nanobind.readthedocs.io/en/latest/refleaks.html#disabling-leak-warnings), and to eventually turn on strict resource leak enforcement for nanobind in drake CI. This issue is to remind us to do the CI strict checking bit.
What's wanted is to add the compile time preprocessor definition NB_ABORT_ON_LEAK to appropriate CI builds, so that leaks will be converted into test failures in CI.
Our current plan is to ship nanobind with resource leak warnings disabled (see https://nanobind.readthedocs.io/en/latest/refleaks.html#disabling-leak-warnings), and to eventually turn on strict resource leak enforcement for nanobind in drake CI. This issue is to remind us to do the CI strict checking bit.
What's wanted is to add the compile time preprocessor definition
NB_ABORT_ON_LEAKto appropriate CI builds, so that leaks will be converted into test failures in CI.