Edgewall Software

Opened 20 years ago

Last modified 20 years ago

#888 closed defect

Timeline produces mktime Error — at Version 1

Reported by: clynx Owned by: Christopher Lenz
Priority: high Milestone: 0.8
Component: timeline Version: devel
Severity: major Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description (last modified by Christopher Lenz)

The following Error occured while Calling the Timeline in my fresh Installation:

Oops… Trac detected an internal error: mktime argument out of range

Everything works except the Timeline …

Python traceback

Traceback (most recent call last):

File "/usr/local/lib/python2.2/site-packages/trac/core.py", line 526, in cgi_start

real_cgi_start()

File "/usr/local/lib/python2.2/site-packages/trac/core.py", line 521, in real_cgi_start

dispatch_request(path_info, args, req, env)

File "/usr/local/lib/python2.2/site-packages/trac/core.py", line 436, in dispatch_request

module.run()

File "/usr/local/lib/python2.2/site-packages/trac/Module.py", line 44, in run

self.render()

File "/usr/local/lib/python2.2/site-packages/trac/Timeline.py", line 201, in render

_from = time.mktime((t[0], t[1], t[2], 23, 59, 59, t[6], t[7], t[8]))

OverflowError: mktime argument out of range

Change History (1)

comment:1 by Christopher Lenz, 20 years ago

Component: general → timeline
Description: modified (diff)
Milestone: → 0.8
Owner: changed from Jonas Borgström to Christopher Lenz
Priority: normal → high
Severity: normal → major
Status: new → assigned

On IrcChannel clynx reported that t was set to (1900, 1, 0, 0, 0, 0, 6, 1, 0). It appears that time.strptime() doesn't raise an exception but return "time zero". Maybe a FreeBSD thing?

Note: See TracTickets for help on using tickets.