- Zope-Dev - Zope lists

zope-tests - OK: 21
by Zope tests summarizer 17 Oct '12

17 Oct '12

This is the summary for test reports received on the zope-tests list between 2012-10-15 00:00:00 UTC and 2012-10-16 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Successful - zopetoolkit_trunk - Build # 45 Successful - zopetoolkit_trunk_app - Build # 29 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results --------------

1 0

zope-tests - FAILED: 1, OK: 20
by Zope tests summarizer 16 Oct '12

16 Oct '12

This is the summary for test reports received on the zope-tests list between 2012-10-14 00:00:00 UTC and 2012-10-15 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Successful - zopetoolkit_trunk - Build # 44 Successful - zopetoolkit_trunk_app - Build # 28 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 [1] winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / ztk_11 py_270_win32 https://mail.zope.org/pipermail/zope-tests/2012-October/068654.html

2 1

Zope Foundation patch policy
by Jens Vagelpohl 16 Oct '12

16 Oct '12

Hi all, During the discussion about new ways to host and manage code in Zope Foundation repositories one omission we had never really addressed became clear: What is the status of patches reaching us by people who have not signed the contributor agreement, e.g. code uploaded to issue trackers, or code checked into Zope Foundation repositories by people other than the original authors? We need to have guidelines that ensure that we don't end up with code exclusively owned by third parties where no ownership assignment has taken place in our repositories. Fortunately the Plone Foundation has considered this exact issue before us and we took their well-written patch policy[1] and adapted it for our own use. Thanks to the Plone Foundation board and all those who drafted their policy. The Zope Foundation board has voted on adopting the following text as the official Zope Foundation patch policy, binding for all Zope Foundation contributors (PDF alert): http://foundation.zope.org/agreements/ZopeFoundation_Patch_Policy.pdf Jens Vagelpohl -- Jens Vagelpohl Secretary, Zope Foundation Board of Directors [1] http://plone.org/foundation/materials/foundation-resolutions/patch-policy-0…

2 1

zope-tests - FAILED: 6, OK: 23
by Zope tests summarizer 15 Oct '12

15 Oct '12

This is the summary for test reports received on the zope-tests list between 2012-10-13 00:00:00 UTC and 2012-10-14 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- [1] Repository policy check found errors in 276 projects Successful - zopetoolkit_trunk - Build # 43 Successful - zopetoolkit_trunk_app - Build # 27 [2] Total languishing bugs for zope2: 5 [3] Total languishing bugs for zope: 71 [4] Total languishing bugs for zopeapp: 1 [5] Total languishing bugs for zopetoolkit: 203 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ZODB_dev py_270_win64 [6] winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED Repository policy check found errors in 276 projects https://mail.zope.org/pipermail/zope-tests/2012-October/068615.html [2] FAILED Total languishing bugs for zope2: 5 https://mail.zope.org/pipermail/zope-tests/2012-October/068614.html [3] FAILED Total languishing bugs for zope: 71 https://mail.zope.org/pipermail/zope-tests/2012-October/068613.html [4] FAILED Total languishing bugs for zopeapp: 1 https://mail.zope.org/pipermail/zope-tests/2012-October/068610.html [5] FAILED Total languishing bugs for zopetoolkit: 203 https://mail.zope.org/pipermail/zope-tests/2012-October/068612.html [6] FAILED winbot / ztk_10 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2012-October/068627.html

3 2

Re: [Zope-dev] TTW leaking of annotions in Plone 4
by Roel Bruggink 15 Oct '12

15 Oct '12

AFAIK this is still open, moved to Zope-Dev. On Sun, Apr 24, 2011 at 12:18 PM, Martin Aspeli <optilude(a)gmx.net> wrote: > Hi, > > On 23 April 2011 19:10, David Glick <dglick(a)gmail.com> wrote: >> On 4/21/11 9:57 AM, Laurence Rowe wrote: >>> >>> On 21 April 2011 10:19, Roel Bruggink<roel(a)fourdigits.nl> wrote: >>>> >>>> Hi, >>>> We noticed that calling @@ on an url shows the annotations of that >>>> object. >>>> This works for anonymous, but only in Plone 4. >>>> See http://plone-demo.sixfeetup.com/@@ . >>> >>> Ok, this is due to the standard view lookup code in >>> ZPublisher.BaseRequest.BaseRequest.traverseName: >>> >>> ob2 = namespaceLookup(ns, nm, ob, self) >>> >>> It's getting the adapter registered in zope.annotations: >>> >>> <adapter >>> for=".interfaces.IAttributeAnnotatable *" >>> provides=".interfaces.IAnnotations" >>> factory=".attribute.AttributeAnnotations" >>> /> >>> >>> I'm not quite sure what this 2-way adapter is for. >>> AttributeAnnotations.__init__ takes an optional context argument which >>> is promptly thrown away. >>> >>> Two ways to fix this: >>> >>> 1. Register a more specific adapter for (IAttributeAnnotatble, >>> IRequest) which would raise a KeyError or something to provoke a >>> NotFound response. >>> >>> 2. Add a __str__ method to AttributeAnnotations so no information is >>> leaked when it is published. >>> >>> 3. Special case traverseName to check that the namespace name is not >>> the empty string. >>> >>> I guess I can see the use-case for allowing @@ in page templates and >>> such, but this is actually prevented by code in >>> OFS.Traversable.Traversable.unrestrictedTraverse which specifically >>> checks for nsParse(name)[1], the namespace name. >>> >>> Perhaps we would be better moving this discussion to zope-dev. It >>> doesn't seem too serious from a security perspective. >> >> A possible long-term solution (involving an API change) would be to make the >> view registration directives register views as adapters to an IBrowserPage >> interface, and then make the view traverser look up adapters to that >> interface instead of (implicitly) to Interface. Then it couldn't find random >> (context,request) adapters that weren't intended to be views and that didn't >> get security declarations. > > I agree this would be much better, but I think it's too big a change > and something we'll need to live with: a lot of code does > getMultiAdapter((context, request,), name="...") to get a view. > > A slightly more clunky but compatible idea may be to just explicitly > check IView.providedBy(obj) during publication? > > Martin -- Roel Bruggink http://www.fourdigits.nl/mensen/roel-bruggink Four Digits BV http://www.fourdigits.nl tel: +31(0)26 4422700

1 0

zope-tests - OK: 21
by Zope tests summarizer 14 Oct '12

14 Oct '12

This is the summary for test reports received on the zope-tests list between 2012-10-12 00:00:00 UTC and 2012-10-13 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Successful - zopetoolkit_trunk - Build # 42 Successful - zopetoolkit_trunk_app - Build # 26 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results --------------

1 0

zope-tests - OK: 21
by Zope tests summarizer 13 Oct '12

13 Oct '12

This is the summary for test reports received on the zope-tests list between 2012-10-11 00:00:00 UTC and 2012-10-12 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Successful - zopetoolkit_trunk - Build # 41 Successful - zopetoolkit_trunk_app - Build # 25 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results --------------

1 0

zope-tests - OK: 20, UNKNOWN: 1
by Zope tests summarizer 12 Oct '12

12 Oct '12

This is the summary for test reports received on the zope-tests list between 2012-10-10 00:00:00 UTC and 2012-10-11 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Successful - zopetoolkit_trunk - Build # 40 Successful - zopetoolkit_trunk_app - Build # 24 [1] UNKNOWN : Zope-trunk Python-2.7.3 : Linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] UNKNOWN UNKNOWN : Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2012-October/068558.html

2 1

zope-tests - OK: 21
by Zope tests summarizer 11 Oct '12

11 Oct '12

This is the summary for test reports received on the zope-tests list between 2012-10-09 00:00:00 UTC and 2012-10-10 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Successful - zopetoolkit_trunk - Build # 39 Successful - zopetoolkit_trunk_app - Build # 23 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results --------------

1 0

Lazy translation domains
by Malthe Borch 10 Oct '12

10 Oct '12

In 2008, the `zope_i18n_allowed_languages` environment setting was introduced to limit the languages for which a message catalog is loaded when you register translations using the "registerTranslation" ZCML directive, and to be able to negotiate a list from a list of available languages. This branch implements a fallback mechanism where: 1) the allowed languages are determined at runtime. 2) translation domains are lazy, and load message catalogs only when required. http://svn.zope.org/zope.i18n/branches/lazy-tds/ \malthe

1 0