[Zope-dev] Zope Tests: 3 OK, 5 Failed
Summary of messages to the zope-tests list. Period Sat Jul 18 12:00:00 2009 UTC to Sun Jul 19 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures - Subject: FAILED (failures=1) : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Sat Jul 18 20:50:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012090.html Subject: FAILED (failures=1) : Zope-2.12-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat Jul 18 20:52:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012091.html Subject: FAILED (failures=7) : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Sat Jul 18 20:54:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012092.html Subject: FAILED (failures=1) : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Sat Jul 18 20:56:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012093.html Subject: FAILED (failures=7) : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Sat Jul 18 20:58:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012094.html Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jul 18 20:44:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012087.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jul 18 20:46:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012088.html Subject: OK : Zope-2.12 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jul 18 20:48:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012089.html ___ 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 )
Re: [Zope-dev] Broken authentication with zope.app.component 3.4.1 BBB code
On Wed, Jul 15, 2009 at 4:08 PM, Marius Gedminasmar...@gedmin.as wrote: ... This is a pretty serious issue, so I'd appreciate some review from people who know about local component registries. The fix is here: http://svn.zope.org/zope.app.component/?rev=101931view=rev Thanks for digging into this. You should use a generation to fix the problem rather hacking __setstate__. The hard part of this is figuring out where to put the generation. I wonder where that standard schema manager is. Maybe you should just create one for zope.app.component. Jim -- Jim Fulton Readability counts. ___ 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 )
Re: [Zope-dev] Broken authentication with zope.app.component 3.4.1 BBB code
On Sun, Jul 19, 2009 at 11:55:45AM -0400, Jim Fulton wrote: On Wed, Jul 15, 2009 at 4:08 PM, Marius Gedminasmar...@gedmin.as wrote: ... This is a pretty serious issue, so I'd appreciate some review from people who know about local component registries. The fix is here: http://svn.zope.org/zope.app.component/?rev=101931view=rev Thanks for digging into this. You should use a generation to fix the problem rather hacking __setstate__. The hard part of this is figuring out where to put the generation. I wonder where that standard schema manager is. Maybe you should just create one for zope.app.component. It used to be in zope.app.generations. I don't know how exactly the coordination for all that works now after the eggsplosion. Note that zope.app.component currently implements most of its BBB via __setstate__ methods that explicitly try to avoid dirtying the objects. I don't know the rationale for that -- maintaining the ability to roll back to ancient Zope without reverting transactions in Data.fs, or perhaps just avoiding write-on-read semantics? That's part of why I asked for a review. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ 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 )
Re: [Zope-dev] Broken authentication with zope.app.component 3.4.1 BBB code
On Sun, Jul 19, 2009 at 4:25 PM, Marius Gedminasmar...@gedmin.as wrote: On Sun, Jul 19, 2009 at 11:55:45AM -0400, Jim Fulton wrote: ... You should use a generation to fix the problem rather hacking __setstate__. The hard part of this is figuring out where to put the generation. I wonder where that standard schema manager is. Maybe you should just create one for zope.app.component. It used to be in zope.app.generations. I don't know how exactly the coordination for all that works now after the eggsplosion. Maybe someone will enlighten us about where it went. :) Note that zope.app.component currently implements most of its BBB via __setstate__ methods that explicitly try to avoid dirtying the objects. I don't know the rationale for that -- maintaining the ability to roll back to ancient Zope without reverting transactions in Data.fs, or perhaps just avoiding write-on-read semantics? That's part of why I asked for a review. I was wondering about that myself. I think this was more a matter of bootstrapping. It may have been that it would have been too hard to write a evolution script because the evolution script might have needed a working component registry. I don't think this is the case here. If we can't find the old schema manager, I'd rather start a new one in here (in zope.app.component.) I think what it has to do is pretty simple -- just check to make sure the __bases__ for the root component registry is correct. Jim -- Jim Fulton ___ 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 )
