Modify ↓
Opened 9 years ago
Closed 9 years ago
#12007 closed enhancement (fixed)
Use lower logging level for "Invalid Date"
| Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
|---|---|---|---|
| Priority: | lowest | Milestone: | 1.0.6 |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: |
Warning is added when timeline |
||
| API Changes: | |||
| Internal Changes: | |||
Description
I see the following rather frequently in the logs (Trac 1.0.6).
2015-03-26 23:40:37,471 Trac[main] WARNING: [81.149.25.66] HTTPInternalError: 500 Invalid Date ("2007-01-17T17:39:21 01:00" is an invalid date, or the date format is not known. Try "MMM d, y" or "YYYY-MM-DDThh:mm:ss±hh:mm" instead.)
Since this is just invalid date entry, we could log at DEBUG level (similar to #12005).
Attachments (0)
Change History (3)
comment:1 by , 9 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 9 years ago
comment:3 by , 9 years ago
| Release Notes: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
Committed to 1.0-stable in [13966], merged to trunk in [13967:13968].
Note:
See TracTickets
for help on using tickets.
Date fields are used in timeline prefs, milestone edit, admin milestone edit and ticket query. Ticket query traps the exceptions. Also, JavaScript pretty much prevents invalid user input. Most likely the frequent errors in the log are coming from bots hitting the timeline page. Proposed change in log:rjollos.git:t12007.