carloea2 opened a new issue, #8152: URL: https://github.com/apache/texera/issues/8152
### What happened? Dashboard date filters use lenient parsing and do not translate parse failures into client errors. Before: a non-date value returns 500, while an impossible calendar date is silently normalized and returns 200. After: malformed and impossible dates return 400, while valid ISO dates remain accepted. ### How to reproduce? 1. Start the local development backend from main. 2. Request `GET /api/dashboard/publicSearch?resourceType=workflow&createDateStart=bogus` and observe HTTP 500. 3. Request the endpoint with `modifiedDateEnd=2026-99-99` and observe HTTP 200. 4. Request the endpoint with `createDateStart=2026-01-01` and observe HTTP 200. ### Version/Branch 1.3.0-incubating-SNAPSHOT (main) ### Commit Hash (Optional) 98588bf2ab49aac65ebf002496eb057670e6fc07 ### What browsers are you seeing the problem on? Not browser-specific. ### Relevant log output The shared date parser is lenient and exposes parsing failures as internal errors. -- 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]
