Aias00 opened a new issue, #833: URL: https://github.com/apache/rocketmq-dashboard/issues/833
### What happened? The AI chat and execute paths pass request DTOs directly into AiService. If a client sends an empty request body or a null DTO reaches the service layer, AiService dereferences the request immediately when logging fields such as mode, conversationId, or command. This can turn a client-side validation problem into a NullPointerException instead of a clear 400-style validation error. ### Expected behavior AI endpoints and service entry points should reject missing request bodies with a clear BusinessException or equivalent 400 response before invoking the LLM gateway. ### Why this matters This belongs to the AI Native / AI-01.1 control-plane surface. The AI entrypoint should return predictable structured errors so the Web Console and future MCP bridge can handle invalid requests safely. ### Candidate fix - Mark AI request bodies as required at controller level - Add service-level null checks for ChatDTO and AiCommandDTO - Add focused unit coverage for null chat and execute requests -- 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]
