Modify ↓
#6706 closed defect (invalid)
milestone cannot have year 2100 ...
Reported by: | ThurnerRupert | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | lowest | Milestone: | |
Component: | general | Version: | |
Severity: | trivial | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
i know that it is hypothetical, but it does not look good. setting a milestone in year 2100 gives:
Traceback (most recent call last): File "/opt/csw/lib/python/site-packages/trac/web/main.py", line 406, in dispatch_request dispatcher.dispatch(req) File "/opt/csw/lib/python/site-packages/trac/web/main.py", line 237, in dispatch resp = chosen_handler.process_request(req) File "/opt/csw/lib/python/site-packages/TracWebAdmin-0.1.2dev_r5911-py2.5.egg/webadmin/web_ui.py", line 119, in process_request path_info) File "/opt/csw/lib/python/site-packages/TracWebAdmin-0.1.2dev_r5911-py2.5.egg/webadmin/ticket.py", line 163, in process_admin_request mil.due = util.parse_date(req.args.get('duedate')) File "/opt/csw/lib/python/site-packages/trac/util/datefmt.py", line 109, in parse_date seconds = time.mktime(date) OverflowError: mktime argument out of range
Attachments (0)
Change History (3)
comment:2 by , 17 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
This is not a Trac bug, it's a limitation of Python and possibly the underlying OS.
comment:3 by , 17 years ago
For what is worth, 0.11 displays a nicer error in that case:
The date "12/15/2107" is outside valid range. Try a date closer to present time.
Note:
See TracTickets
for help on using tickets.