narrowizard opened a new issue, #8516: URL: https://github.com/apache/incubator-devlake/issues/8516
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened When attempting to update a blueprint using the PATCH API and setting the `timeAfter` parameter to `null`, the value is unexpectedly converted to `0001-01-01T00:00:00Z`. ### What do you expect to happen I expect that setting `timeAfter` to `null` should effectively remove any time restriction for data synchronization, meaning the parameter should remain `null` or be interpreted as 'no time limit' for data collection. ### How to reproduce 1. Identify an existing blueprint or create a new one in Apache DevLake. 2. Use the DevLake PATCH API endpoint for blueprints (e.g., `/api/blueprints/{blueprintId}`). 3. In the request body, set the `timeAfter` field to `null` (e.g., `{"timeAfter": null}`). 4. Send the PATCH request. 5. Observe the updated blueprint's `timeAfter` value, which will be `0001-01-01T00:00:00Z` instead of `null`. ### Anything else <img width="2560" height="1600" alt="Image" src="https://github.com/user-attachments/assets/0e9455a2-0a2e-4866-b83d-c337d7aa4558"; /> ### Version main ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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: dev-unsubscr...@devlake.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
