Re: [Zope-dev] cPickleCache endless loop...

2004-01-26 Thread Toby Dickenson
On Friday 23 January 2004 17:08, Tim Peters wrote: It looks like ghostifying your self triggers self.__del__(). Then the __del__ method unghostifies self, which has the side effect of moving self to the MRU end of the ring, which in turn means the list traversal will visit self *again*.

[Zope-dev] ZODB load state error

2004-01-26 Thread Thyb
Hi, I just found this in my Zope log file. After this error the Zope system stopped. No wonder, but certainly not because of physical memory error. What could be the problem? My config is: AiX 5.2 Python 2.3.2 Zope 2.7.0-b3 Apache 1.3.26 The error message: 2004-01-25T02:55:21 ERROR(200) ZODB

Re: [Zope-dev] ZODB load state error

2004-01-26 Thread Chris Withers
Thyb wrote: The error message: 2004-01-25T02:55:21 ERROR(200) ZODB Couldn't load state for 3ef2 Traceback (most recent call last): File /opt/freeware/zope/lib/python/ZODB/Connection.py, line 564, in setstate self._set_ghost_state(obj, p) File

Re: [Zope-dev] ZODB load state error

2004-01-26 Thread Toby Dickenson
On Monday 26 January 2004 12:08, Thyb wrote: What could be the problem? That indicates that you are out of memory. If that doesnt seem right, maybe your storage is corrupt in a manner that the unpickler interprets as something with a huge memory footprint. -- Toby Dickenson

[Zope-dev] ZODB 3.3 in Zope 3 status

2004-01-26 Thread Jim Fulton
Fred Drake and I have been working on getting Zope 3 working with ZODB 3.3. See: http://zope.org/Wikis/ZODB/PersistentCodeImplementationPlan (which is part of the Zope 2,8 plan) We are currently working on milestone 2. I *hope* to get this done early this week. When we think everything is

Re: [Zope-dev] cPickleCache endless loop...

2004-01-26 Thread Paul Winkler
On Mon, Jan 26, 2004 at 08:59:36AM +, Chris Withers wrote: Paul Winkler wrote: On Fri, Jan 23, 2004 at 12:08:27PM -0500, Tim Peters wrote: def __del__(self): print About to destroy: , self.id I don't know what your intention is there, but fwiw, if what you're *really*

RE: [Zope-dev] ZODB load state error

2004-01-26 Thread Tim Peters
[Tibor Tolgyesi] I just found this in my Zope log file. After this error the Zope system stopped. No wonder, but certainly not because of physical memory error. What could be the problem? My config is: AiX 5.2 Python 2.3.2 Zope 2.7.0-b3 Apache 1.3.26 The error message:

RE: [Zope-dev] cPickleCache endless loop...

2004-01-26 Thread Tim Peters
[Tim Peters] It looks like ghostifying your self triggers self.__del__(). Then the __del__ method unghostifies self, which has the side effect of moving self to the MRU end of the ring, which in turn means the list traversal will visit self *again*. When it does, same thing happens all over

Re: [Zope-dev] cPickleCache endless loop...

2004-01-26 Thread Toby Dickenson
On Monday 26 January 2004 17:22, Tim Peters wrote: It's actually that the number of __del__-resurrecting objects *plus* the number of non-ghostifiable objects in cache is larger than the cache target size, right? Yes, Right. That is more achievable than I thought. -- Toby Dickenson

[Zope-dev] Re: app = Zope.app() backwards incompatibility notice / discussion

2004-01-26 Thread Gerry Kirk
Chris McDonough wrote: Note that FWIW, you can also do (on UNIX): zopectl run scriptname .. which will run a script with the name app set up as the root Zope application object. This might be the easiest way to run scripts which need to operate against Zope objects going forward. - C I

[Zope-dev] Re: 2.6.4.c1 still problem with security

2004-01-26 Thread Tres Seaver
robert rottermann wrote: Hi there, I am using zope from cvs Zope-2_6-branch. I still get the following assertion in a DCWorkflow which worked flawlessly in 2.6.2 Thanks for any pointers Robert, I have just checked in changes to the bindings computation which should resolve your issues. Could

[Zope-dev] ConflictError in BTreeFolder2

2004-01-26 Thread Florent Guillaume
FYI: I've fixed BTreeFolder2 to properly re-raise ConflictError in _delObject and not swallow it during beforeDelete cleanups. This is the same fix that was done in ObjectManager. Florent -- Florent Guillaume, Nuxeo (Paris, France) +33 1 40 33 79 87 http://nuxeo.com mailto:[EMAIL PROTECTED]