Hi Team, While running regression tests locally, I encountered a panic caused by an assertion failure.
Upon investigation, I noticed that enable-cassert is currently disabled for Cloudberry's panic/build configuration. This concerns me because, without this flag enabled, assertion checks are completely skipped during code merges, which could potentially allow critical bugs to slip into the codebase undetected. Is there a specific reason or historical context as to why we do not have enable-cassert enabled? I would appreciate your insights on this, and perhaps we should consider enabling it to improve our test coverage and code reliability. Best regards, Jinbao Chen
