You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 31, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 31, 2026. It is now read-only.
The DateTime.TryParse fallback will successfully parse time-only strings like "3:00 PM" into a DateTime with the default date (0001-01-01). Since the code returns this as a valid parsed result, callers can end up with nonsensical ancient timestamps. If time-only inputs are meant to be supported, anchor them to now.Date (in the user's timezone) before converting to UTC; otherwise consider rejecting them and requiring the explicit fuzzy format (e.g., "at 3pm").
changed the title [-]The `DateTime.TryParse` fallback will successfully parse time-only strings like "3:00 PM" into a `DateTime` with the default date (0001-01-01). Since the code returns this as a valid parsed result, callers can end up with nonsensical ancient timestamps. If time-only inputs are meant to be supported, anchor them to `now.Date` (in the user's timezone) before converting to UTC; otherwise consider rejecting them and requiring the explicit fuzzy format (e.g., "at 3pm").[/-][+]DateTime.TryParse Issue[/+]on Feb 23, 2026
Activity
[-]The `DateTime.TryParse` fallback will successfully parse time-only strings like "3:00 PM" into a `DateTime` with the default date (0001-01-01). Since the code returns this as a valid parsed result, callers can end up with nonsensical ancient timestamps. If time-only inputs are meant to be supported, anchor them to `now.Date` (in the user's timezone) before converting to UTC; otherwise consider rejecting them and requiring the explicit fuzzy format (e.g., "at 3pm").[/-][+]DateTime.TryParse Issue[/+]