Ticket #7355 (closed defect: fixed)

Opened 2 years ago

Last modified 1 month ago

timestamp out of range for platform time_t error with Trac 0.12 (suggested patch is now attached)

Reported by: eric.portelance@inm.com Assigned to: hoessler
Priority: normal Component: EstimationToolsPlugin
Severity: normal Keywords:
Cc: scottj@glasstowerstudios.com Trac Release: 0.12

Description

After installing Trac 0.12 we are getting a "timestamp out of range for platform time_t" error.

Attachments

datefmt.diff (1.9 kB) - added by bjorn@wololo.org on 07/09/10 16:16:28.
use new date format conversion method as req 0.12+
t7355-to_utimestamp_compat-r5360.diff (2.3 kB) - added by osimons on 07/11/10 23:58:35.
Updated patch that should support both 0.11 and 0.12.

Change History

07/08/10 22:21:19 changed by osimons

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)?

07/09/10 16:16:28 changed by bjorn@wololo.org

  • attachment datefmt.diff added.

use new date format conversion method as req 0.12+

07/09/10 16:18:12 changed by bjorn

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.

07/09/10 16:24:03 changed by anonymous

  • summary changed from timestamp out of range for platform time_t error with Trac 0.12 to timestamp out of range for platform time_t error with Trac 0.12 (suggested patch is now attached).

07/11/10 23:58:35 changed by osimons

  • attachment t7355-to_utimestamp_compat-r5360.diff added.

Updated patch that should support both 0.11 and 0.12.

07/12/10 00:02:11 changed by osimons

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.

07/17/10 14:35:08 changed by hoessler

  • status changed from new to assigned.

If someone could verify that it works on 0.12, I will apply osimons patch on trunk.

07/21/10 09:05:47 changed by bjornharrtell

Verified as working on 0.12, nice work making it compatible.

07/24/10 15:35:55 changed by hoessler

  • status changed from assigned to closed.
  • resolution set to fixed.

(In [8296]) applied patch by bjorn@wololo.org and osimons to support trac 0.12. Fixes #7355.

11/01/10 02:09:31 changed by scottj@glasstowerstudios.com

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?

11/01/10 02:09:46 changed by anonymous

  • cc set to scottj@glasstowerstudios.com.

(follow-up: ↓ 11 ) 12/27/11 21:12:00 changed by anonymous

fast fix:

echo "update wiki set time= substr(time, 0, length(time)-6);" | sqlite3 /var/trac/db/trac.db

(in reply to: ↑ 10 ) 12/27/11 21:21:09 changed by osimons

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???

Add/Change #7355 (timestamp out of range for platform time_t error with Trac 0.12 (suggested patch is now attached))




Change Properties
Action