realAaronWu opened a new pull request, #442:
URL: https://github.com/apache/paimon-cpp/pull/442
> VALIDATION DRAFT for actual CPU CI. Not requesting upstream review or
Ready.
### Purpose
Refs #435; follow-up to #437.
Clear the caller's moved-from `std::function` before checking whether a
rejected
callback's capture was released. A moved-from function can retain a
small-buffer
target under libc++, producing a false test failure despite correct executor
cleanup. Both resets occur after fault injection is disarmed.
All fault-fired/caught, accepted-prefix, callback-run, recovery and shutdown
assertions remain. No production executor behavior changes.
### Tests
- Actual executor/status/test TUs and GTest with real libc++18 headers,
x86_64
macOS: original tests fail release assertions; the fixed tests pass. The
old
pre-#437 executor still fails the startup ownership/run checks; its queue
case
passes as expected. This is not Linux libc++/GNU-wrap qualification.
- Darwin arm64: all 14 actual executor cases pass normally, with ASan/UBSan
and
with TSan, using a scratch Mach-O allocation adapter. Linux-specific
assertions
are not compiled. Apple does not support the requested local leak checks.
- Fresh Linux GCC15.3/libstdc++ all-target build and the two required
submission
tests passed. Full configured-suite qualification, scoped Linux sanitizers,
native mutation and final runtime provenance remain pending.
- Published-head CPU CI will establish the actual supported matrix.
Historical
#437 checks do not qualify this follow-up; no full runtime approval is
claimed.
### API and Format
No public API, storage format, or production-code changes.
### Documentation
No new feature or user-facing behavior.
### Generative AI tooling
Generated-by: OpenAI Codex (desktop session; runtime version not exposed)
--
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]
