#7355 closed defect (fixed)
timestamp out of range for platform time_t error with Trac 0.12 (suggested patch is now attached)
| Reported by: | Owned by: | Joachim Hoessler | |
|---|---|---|---|
| Priority: | normal | Component: | EstimationToolsPlugin |
| Severity: | normal | Keywords: | |
| Cc: | scottj@… | Trac Release: | 0.12 |
Description
After installing Trac 0.12 we are getting a "timestamp out of range for platform time_t" error.
Attachments (2)
Change History (13)
comment:1 Changed 14 years ago by
Changed 14 years ago by
| Attachment: | datefmt.diff added |
|---|
use new date format conversion method as req 0.12+
comment:2 Changed 14 years ago by
I think he is hitting a bug that I think I have fixed in attached patch. The problem is that 0.12 uses new timestamp format:
http://trac.edgewall.org/wiki/TracDev/ApiChanges/0.12#Timestampstorageindatabase
Not sure if I've messed up UTM zone consideration though.
comment:3 Changed 14 years ago by
| Summary: | timestamp out of range for platform time_t error with Trac 0.12 → timestamp out of range for platform time_t error with Trac 0.12 (suggested patch is now attached) |
|---|
Changed 14 years ago by
| Attachment: | t7355-to_utimestamp_compat-r5360.diff added |
|---|
Updated patch that should support both 0.11 and 0.12.
comment:4 Changed 14 years ago by
Thanks for the patch. I've updated it, and made it work across Trac versions to avoid branching just for this. Please try attachment:t7355-to_utimestamp_compat-r5360.diff
Untested on 0.12 by me, so please report back after testing.
comment:5 Changed 14 years ago by
| Status: | new → assigned |
|---|
If someone could verify that it works on 0.12, I will apply osimons patch on trunk.
comment:7 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:8 Changed 14 years ago by
I'm still getting this error with BurndownChart, after pulling from trunk and building r9029. Do I need to do anything special to reconfigure the plugin after installation?
comment:9 Changed 14 years ago by
| Cc: | scottj@… added; anonymous removed |
|---|
comment:10 follow-up: 11 Changed 13 years ago by
fast fix:
echo "update wiki set time= substr(time, 0, length(time)-6);" | sqlite3 /var/trac/db/trac.db
comment:11 Changed 13 years ago by
Replying to anonymous:
fast fix:
echo "update wiki set time= substr(time, 0, length(time)-6);" | sqlite3 /var/trac/db/trac.db
This is not a fast fix for anything. It is a super-fast way of making your Trac 0.12+ wiki think it is ~42 years back in time... Don't run it!
Speaking of, how can changing timestamps in wiki table ever affect the ticket timestamps that the EstimationToolsPlugin uses to render ticket graphs and stats???
Traceback, please. Use Trac debug logging to get the full error from the server. Anything else needed to reproduce this (like macro or macro options)?