Ticket #888 (closed defect: fixed)
Opened 8 years ago
Last modified 8 years ago
Timeline produces mktime Error
| Reported by: | clynx | Owned by: | cmlenz |
|---|---|---|---|
| Priority: | high | Milestone: | 0.8 |
| Component: | timeline | Version: | devel |
| Severity: | major | Keywords: | |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description (last modified by cmlenz) (diff)
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
Attachments
Change History
comment:1 Changed 8 years ago by cmlenz
- Component changed from general to timeline
- Description modified (diff)
- Milestone set to 0.8
- Owner changed from jonas to cmlenz
- Priority changed from normal to high
- Severity changed from normal to major
- Status changed from new to assigned
comment:2 Changed 8 years ago by cmlenz
Comment should have been doesn't raise an exception if the string to parse is empty.
comment:3 Changed 8 years ago by cmlenz
- Resolution set to fixed
- Status changed from assigned to closed
Fixed in [1030].
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?