On Thu, Feb 24, 2005 at 02:58:01PM -0500, Chris McDonough wrote: > On Thu, 2005-02-24 at 14:57, Paul Winkler wrote: > > On Thu, Feb 24, 2005 at 02:52:45PM -0500, Chris McDonough wrote: > > > Two words: *hurt system*. Please, let me kill it. > > > > Interesting. How on earth did you determine that? > > Womanly intuition. > > > > > You think it has to do with registering help for > > PluginIndexes? I'm gonna go test that theory - > > i'll hack registerHelp() to no-op. > > That's a good verifier.
Well, no joy. I hacked ProductContext.register* to return from the first line, so even registerClass() now does nothing. Barf, I still get the ConflictError. Twiddling around with some old suggestions from Dieter Maurer (see http://aspn.activestate.com/ASPN/Mail/Message/Zope-CMF/1978842 ), I added a _p_jar.sync() where he suggested - right before the final "except:" in initialize_product(). No joy. But - duh - my traceback clearly shows the ConflictError happens before that, in the call to get_transaction().commit(). SO I moved the call to app._p_jar.sync() to right before hte call to get_transaction().commit(). Aaaand... no more ConflictError. Weird weird weird. I'd be happy to check this in to cvs / svc, except that A) I have no clue how to write a test that exercises the bug, and B) so far nobody seems to understand what's really happening. If nobody objects, I wouldnt' mind checking the fix in anyway :-) -- Paul Winkler http://www.slinkp.com _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )