fgerlits opened a new pull request, #2243: URL: https://github.com/apache/nifi-minifi-cpp/pull/2243
- make the memcheck CI job fail if valgrind finds issues - fix a small leak in opc.cpp: the default stdout logger allocated by UA_Client_new was not freed when we replaced it with our own logger (and it was also cached elsewhere inside the client) - fix a test code leak in PutOpcProcessorTests - suppress "still reachable" valgrind logs: these come from static objects, and are not a problem - suppress some "possible loss" valgrind logs: these also come from long-lived objects which are not really leaked The valgrind.supp file was created using Claude Code. --- Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [x] Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically main)? - [x] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
