Having the exact problem, but I think I got it to go away (though not completely, see below): I just noticed in the utilities directory there are, obviously, some python-written utilities. I used one, bbb.py, to convert the Data.bbb.in file (which is ZODB2) to Data.fs (ZODB3). I had previously stopped the Zope process, so I restarted and got neither the "FS21 warn" statements nor the over flow errors. But, just checking, I now get an attribute error when I try to commit changes to a DTML doc/method. The traceback: <!-- Traceback (innermost last): File C:\Zope\Zope-2.0.0a3-src\lib\python\ZPublisher\Publish.py, line 256, in publish_module File C:\Zope\Zope-2.0.0a3-src\lib\python\ZPublisher\Publish.py, line 165, in publish File C:\Zope\Zope-2.0.0a3-src\lib\python\BoboPOS\SingleThreadedTransaction.py, line 190, in commit AttributeError: __inform_commit__ --> And now this problem has mysteriously gone away. I appear to get this when editing a Zope object for the first time. In spite of the error the changes I make still get committed, and with subsequent changes the error does not occur. Could this be an artifact of the program used to convert from ZODB2 format to ZODB3? Good luck, John
-----Original Message----- From: Toby Dickenson [SMTP:tdickenson@oriongroup.co.uk] Sent: Thursday, June 24, 1999 5:01 AM To: zope@zope.org Subject: [Zope] timestamp problem on NT
Zope 2.0 alpha 3 seems to be getting confused over timestamps on NT. This is a typicial traceback, from trying to view the dtml edit page of standard_html_footer:
Traceback (innermost last): File lib\python\ZPublisher\Publish.py, line 256, in publish_module File lib\python\ZPublisher\Publish.py, line 161, in publish File lib\python\ZPublisher\mapply.py, line 154, in mapply (Object: manage_main) File lib\python\ZPublisher\Publish.py, line 98, in call_object (Object: manage_main) File lib\python\App\special_dtml.py, line 120, in __call__ (Object: manage_main) (Info: D:\Program Files\Zope-2.0.0a3-src\lib\python\OFS/documentEdit. dtml) File lib\python\DocumentTemplate\DT_String.py, line 514, in __call__ (Object: manage_main) File lib\python\App\PersistentExtra.py, line 104, in bobobase_modification_time (Object: standard_html_header) File D:\Program Files\Zope-2.0.0a3-src\lib\python\DateTime\DateTime.py , line 534, in __init__ OverflowError: float too large to convert
Curious to see what that float value was, I added a "print t" on line 533 of DateTime. I see the value 77108275237.6, which is definitely out of range. Curiously, I see exactly the same number after shutting down zope, clearing the var directory, and restarting.
I also get two warnings on restarting with an empty var:
FS21 warn: D:\Program Files\Zope-2.0.0a3-src/var/Data.fs truncated, possibly due to damaged records at 4 FS21 warn: D:\Program Files\Zope-2.0.0a3-src/var/Data.fs Database records in the future
Any thoughts?
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )