Re: [Zope-CMF] Still Failing - CMF-trunk_Zope-trunk - Build # 645
I don't know how to properly fix this. For now I upgrade to newest setuptools before boostrapping, then CMF does not fail. Here is the Bug report for the issue I experienced. https://github.com/buildout/buildout/issues/237 On 11.02 09:50, Jenkins wrote: CMF-trunk_Zope-trunk - Build # 645 - Still Failing: Check console output at https://jenkins.starzel.de/job/CMF-trunk_Zope-trunk/645/ to view the results. ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests signature.asc Description: Digital signature ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
[Zope-CMF] Testmail, you can ignore it
xxx signature.asc Description: Digital signature ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Successful - CMF-trunk_Zope-trunk - Build # 611
On 09.01 12:06, Charlie Clark wrote: Hiya Patrick, Am .01.2015, 11:48 Uhr, schrieb Patrick Gerken ger...@starzel.de: I hope you don't mind my jenkins to post here directly. I never managed to enter cmf-tests list and since I am the only tester, I figured I can send here directly. No problem and thanks for adding it. Any chance you can add coverage information? Or isn't that possible with the Zope testing toolchain? No problem, we do this for a bunch of (private) jobs on this server already. But for now I just put this on my todo list. Can you do anything about the certificate error on your site? Lets wait for firefox and eff in the summer: https://letsencrypt.org/ Until then, this will stay a self signed certificate. Best regards, Patrick signature.asc Description: Digital signature ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Successful - CMF-trunk_Zope-trunk - Build # 611
Hi, I hope you don't mind my jenkins to post here directly. I never managed to enter cmf-tests list and since I am the only tester, I figured I can send here directly. I can, if you want, limit the mails to events of failures. The build runs daily, as you can see by the number, for quite a while already. It was always stable. I guess that means everybody here is a perfect developer who never makes mistakes. Best regards, Patrick On 09.01 10:46, Jenkins wrote: CMF-trunk_Zope-trunk - Build # 611 - Successful: Check console output at https://jenkins.starzel.de/job/CMF-trunk_Zope-trunk/611/ to view the results. ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests signature.asc Description: Digital signature ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-dev] zope-tests - FAILED: 9, OK: 11
I am messing with my chef setup. I didn't figure out how to do this on a test environment yet. Sorry for the noise. On Thu, Sep 5, 2013 at 9:29 AM, Marius Gedminas mar...@gedmin.as wrote: On Thu, Sep 05, 2013 at 08:53:54AM +0200, Adam GROSZER wrote: On 09/05/2013 02:58 AM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/04/2013 07:00 PM, Zope tests summarizer wrote: [1]Failure - zopetoolkit_trunk - Build # 379 Fixed - zopetoolkit_trunk - Build # 389 [2]Still Failing - zopetoolkit_trunk - Build # 380 [3]Still Failing - zopetoolkit_trunk - Build # 381 [4]Still Failing - zopetoolkit_trunk - Build # 382 [5]Still Failing - zopetoolkit_trunk - Build # 383 [6]Still Failing - zopetoolkit_trunk - Build # 384 [7]Still Failing - zopetoolkit_trunk - Build # 385 [8]Still Failing - zopetoolkit_trunk - Build # 386 [9]Still Failing - zopetoolkit_trunk - Build # 387 Anybody understand what caused those errors? There isn't any activity during the range of time represented by those failures. It looks like the distribute/setuptools hell broke in. Maybe Patrick changed something? I'm guessing an upgrade of /usr/local/bin/virtualenv-2.7 to some version that ignores --distribute (since it's superseded by setuptools). Unfortunately buildout's bootstrap.py really really *really* wants to have distribute. BTW the last build was successful, so Patrick figured out how to appease bootstrap.py in the end. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 14, OK: 7
Hi, zopetoolkit-trunk under linux is fine. I create a fresh buildout every time, now I have to create a virtualenv with --distribute, then I have to upgrade setuptools. Until I tested all combinations, I had a bunch of failed test runs. I have a feeling I'll need to buy rubber chickens for the next iterations. On Thu, Jul 11, 2013 at 1:01 AM, Zope tests summarizer nore...@zope.orgwrote: This is the summary for test reports received on the zope-tests list between 2013-07-09 00:00:00 UTC and 2013-07-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 [1]Failure - zopetoolkit_trunk - Build # 320 Fixed - zopetoolkit_trunk - Build # 319 Fixed - zopetoolkit_trunk - Build # 324 [2]Still Failing - zopetoolkit_trunk - Build # 318 [3]Still Failing - zopetoolkit_trunk - Build # 321 [4]Still Failing - zopetoolkit_trunk - Build # 322 [5]Still Failing - zopetoolkit_trunk - Build # 323 [6]winbot / ZODB_dev py_265_win32 [7]winbot / ZODB_dev py_265_win64 [8]winbot / ZODB_dev py_270_win32 [9]winbot / ZODB_dev py_270_win64 [10] winbot / z3c.layer.pagelet_py_265_32 [11] winbot / zc.sourcefactory_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 [12] winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 [13] winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 [14] winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Failure - zopetoolkit_trunk - Build # 320 https://mail.zope.org/pipermail/zope-tests/2013-July/077754.html [2]FAILED Still Failing - zopetoolkit_trunk - Build # 318 https://mail.zope.org/pipermail/zope-tests/2013-July/077752.html [3]FAILED Still Failing - zopetoolkit_trunk - Build # 321 https://mail.zope.org/pipermail/zope-tests/2013-July/077755.html [4]FAILED Still Failing - zopetoolkit_trunk - Build # 322 https://mail.zope.org/pipermail/zope-tests/2013-July/077756.html [5]FAILED Still Failing - zopetoolkit_trunk - Build # 323 https://mail.zope.org/pipermail/zope-tests/2013-July/077757.html [6]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-July/077767.html [7]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077768.html [8]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-July/077769.html [9]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/00.html [10] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/077751.html [11] FAILED winbot / zc.sourcefactory_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/077750.html [12] FAILED winbot / ztk_10 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077761.html [13] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077764.html [14] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077766.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Maintenance of zope mailman
Hi, last month, all Mailing lists were unavailable for a week. On twitter, I saw it took some time to set up due to time constraints. Are there plans to increase the admin team to avoid time constraint issues? Regarding Mailman itself, after we lost regular cmf tests, I set up my jenkins to run tests for CMF too. Unfortunately I cannot send mails to the cmf-tests mailing list. My subscription request from 5.5. is still in the moderation queue. Do we still have moderators for mailman? I expect that both services do not involve a lot of ongoing work. The administration is probably time intensive in the beginning to get to know how everything is set up. If thats the case I happily volunteer. Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 88, OK: 6
Hi, was the summarizer on the same machine? What is needed to get it running again? Best regards, Patrick 2013/6/13 Zope tests summarizer nore...@zope.org This is the summary for test reports received on the zope-tests list between 2013-06-11 00:00:00 UTC and 2013-06-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 # 294 [1]winbot / ZEO_py_265_32 [2]winbot / ZODB_dev py_265_win32 [3]winbot / ZODB_dev py_265_win64 [4]winbot / ZODB_dev py_270_win32 [5]winbot / ZODB_dev py_270_win64 [6]winbot / z3c.authenticator_py_265_32 [7]winbot / z3c.breadcrumb_py_265_32 [8]winbot / z3c.configurator_py_265_32 [9]winbot / z3c.contents_py_265_32 [10] winbot / z3c.coverage_py_265_32 [11] winbot / z3c.datagenerator_py_265_32 [12] winbot / z3c.form_py_265_32 [13] winbot / z3c.formui_py_265_32 [14] winbot / z3c.json_py_265_32 [15] winbot / z3c.jsontree_py_265_32 [16] winbot / z3c.language.switch_py_265_32 [17] winbot / z3c.layer.pagelet_py_265_32 [18] winbot / z3c.layer.ready2go_py_265_32 [19] winbot / z3c.macro_py_265_32 [20] winbot / z3c.menu.ready2go_py_265_32 [21] winbot / z3c.pagelet_py_265_32 [22] winbot / z3c.password_py_265_32 [23] winbot / z3c.ptcompat_py_265_32 [24] winbot / z3c.sampledata_py_265_32 [25] winbot / z3c.table_py_265_32 [26] winbot / z3c.tabular_py_265_32 [27] winbot / z3c.template_py_265_32 [28] winbot / z3c.testing_py_265_32 [29] winbot / zc.lockfile_py_265_32 [30] winbot / zc.queue_py_265_32 [31] winbot / zc.sourcefactory_py_265_32 [32] winbot / zope.app.appsetup_py_265_32 [33] winbot / zope.app.authentication_py_265_32 [34] winbot / zope.app.dependable_py_265_32 [35] winbot / zope.app.http_py_265_32 [36] winbot / zope.app.locales_py_265_32 [37] winbot / zope.app.publication_py_265_32 [38] winbot / zope.applicationcontrol_py_265_32 [39] winbot / zope.authentication_py_265_32 [40] winbot / zope.browsermenu_py_265_32 [41] winbot / zope.browserpage_py_265_32 [42] winbot / zope.browserresource_py_265_32 [43] winbot / zope.catalog_py_265_32 [44] winbot / zope.component_py_265_32 [45] winbot / zope.componentvocabulary_py_265_32 [46] winbot / zope.container_py_265_32 [47] winbot / zope.contentprovider_py_265_32 [48] winbot / zope.copypastemove_py_265_32 [49] winbot / zope.datetime_py_265_32 [50] winbot / zope.deferredimport_py_265_32 [51] winbot / zope.dublincore_py_265_32 [52] winbot / zope.error_py_265_32 [53] winbot / zope.exceptions_py_265_32 [54] winbot / zope.formlib_py_265_32 [55] winbot / zope.generations_py_265_32 [56] winbot / zope.i18n_py_265_32 [57] winbot / zope.index_py_265_32 [58] winbot / zope.intid_py_265_32 [59] winbot / zope.keyreference_py_265_32 [60] winbot / zope.location_py_265_32 [61] winbot / zope.login_py_265_32 [62] winbot / zope.mimetype_py_265_32 [63] winbot / zope.minmax_py_265_32 [64] winbot / zope.pagetemplate_py_265_32 [65] winbot / zope.password_py_265_32 [66] winbot / zope.pluggableauth_py_265_32 [67] winbot / zope.principalannotation_py_265_32 [68] winbot / zope.principalregistry_py_265_32 [69] winbot / zope.processlifetime_py_265_32 [70] winbot / zope.ptresource_py_265_32 [71] winbot / zope.publisher_py_265_32 [72] winbot / zope.ramcache_py_265_32 [73] winbot / zope.renderer_py_265_32 [74] winbot / zope.security_py_265_32 [75] winbot / zope.securitypolicy_py_265_32 [76] winbot / zope.sendmail_py_265_32 [77] winbot / zope.sequencesort_py_265_32 [78] winbot / zope.session_py_265_32 [79] winbot / zope.site_py_265_32 [80] winbot / zope.structuredtext_py_265_32 [81] winbot / zope.tal_py_265_32 [82] winbot / zope.tales_py_265_32 [83] winbot / zope.testrunner_py_265_32 [84] winbot / zope.traversing_py_265_32 [85] winbot / zope.viewlet_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 [86] winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 [87] winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 [88] winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED winbot / ZEO_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/076597.html [2]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-June/076538.html [3]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-June/076539.html [4]FAILED winbot / ZODB_dev py_270_win32
Re: [Zope-dev] zope-tests - FAILED: 78, OK: 12
2013/5/14 Marius Gedminas mar...@gedmin.as On Tue, May 14, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 266 ImportError: persistent This is also some sort of buildout issue, btw. [2]winbot / ZEO_py_265_32 The two blob path issues [3]winbot / z3c.authenticator_py_265_32 [4]winbot / z3c.breadcrumb_py_265_32 [5]winbot / z3c.configurator_py_265_32 [6]winbot / z3c.contents_py_265_32 [7]winbot / z3c.coverage_py_265_32 [8]winbot / z3c.datagenerator_py_265_32 [9]winbot / z3c.form_py_265_32 [10] winbot / z3c.formui_py_265_32 [11] winbot / z3c.json_py_265_32 [12] winbot / z3c.layer.pagelet_py_265_32 [13] winbot / z3c.layer.ready2go_py_265_32 [14] winbot / z3c.macro_py_265_32 [15] winbot / z3c.menu.ready2go_py_265_32 [16] winbot / z3c.pagelet_py_265_32 [17] winbot / z3c.password_py_265_32 [18] winbot / z3c.ptcompat_py_265_32 [19] winbot / z3c.sampledata_py_265_32 [20] winbot / z3c.table_py_265_32 [21] winbot / z3c.tabular_py_265_32 [22] winbot / z3c.template_py_265_32 [23] winbot / z3c.testing_py_265_32 [24] winbot / zc.lockfile_py_265_32 [25] winbot / zc.queue_py_265_32 [26] winbot / zc.sourcefactory_py_265_32 [27] winbot / zope.app.authentication_py_265_32 [28] winbot / zope.app.http_py_265_32 [29] winbot / zope.app.locales_py_265_32 [30] winbot / zope.app.publication_py_265_32 [31] winbot / zope.applicationcontrol_py_265_32 [32] winbot / zope.authentication_py_265_32 [33] winbot / zope.browsermenu_py_265_32 [34] winbot / zope.browserpage_py_265_32 [35] winbot / zope.browserpage_py_265_32 [36] winbot / zope.browserresource_py_265_32 [37] winbot / zope.catalog_py_265_32 [38] winbot / zope.component_py_265_32 [39] winbot / zope.componentvocabulary_py_265_32 [40] winbot / zope.container_py_265_32 [41] winbot / zope.contentprovider_py_265_32 [42] winbot / zope.copypastemove_py_265_32 [43] winbot / zope.datetime_py_265_32 [44] winbot / zope.deferredimport_py_265_32 [45] winbot / zope.dublincore_py_265_32 [46] winbot / zope.error_py_265_32 [47] winbot / zope.exceptions_py_265_32 [48] winbot / zope.formlib_py_265_32 [49] winbot / zope.generations_py_265_32 [50] winbot / zope.i18n_py_265_32 [51] winbot / zope.index_py_265_32 [52] winbot / zope.intid_py_265_32 [53] winbot / zope.keyreference_py_265_32 [54] winbot / zope.location_py_265_32 [55] winbot / zope.login_py_265_32 [56] winbot / zope.mimetype_py_265_32 [57] winbot / zope.minmax_py_265_32 [58] winbot / zope.pagetemplate_py_265_32 [59] winbot / zope.password_py_265_32 [60] winbot / zope.pluggableauth_py_265_32 [61] winbot / zope.principalannotation_py_265_32 [62] winbot / zope.principalregistry_py_265_32 [63] winbot / zope.processlifetime_py_265_32 [64] winbot / zope.ptresource_py_265_32 [65] winbot / zope.publisher_py_265_32 [66] winbot / zope.ramcache_py_265_32 [67] winbot / zope.renderer_py_265_32 [68] winbot / zope.security_py_265_32 [69] winbot / zope.securitypolicy_py_265_32 [70] winbot / zope.sendmail_py_265_32 [71] winbot / zope.sequencesort_py_265_32 [72] winbot / zope.session_py_265_32 [73] winbot / zope.site_py_265_32 [74] winbot / zope.structuredtext_py_265_32 [75] winbot / zope.tal_py_265_32 [76] winbot / zope.tales_py_265_32 [77] winbot / zope.traversing_py_265_32 [78] winbot / zope.viewlet_py_265_32 Distribute/buildout issue. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 8, OK: 12
2013/4/12 Zope tests summarizer nore...@zope.org This is the summary for test reports received on the zope-tests list between 2013-04-10 00:00:00 UTC and 2013-04-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 [1]Failure - zopetoolkit_trunk - Build # 231 [2]Failure - zopetoolkit_trunk_app - Build # 169 [3]Still Failing - zopetoolkit_trunk - Build # 230 [4]Still Failing - zopetoolkit_trunk - Build # 232 [5]Still Failing - zopetoolkit_trunk - Build # 233 [6]Still Failing - zopetoolkit_trunk - Build # 234 I am in the process of moving my jenkins to a new machine. Sorry for the noise. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
2013/3/27 Zope tests summarizer nore...@zope.org This is the summary for test reports received on the zope-tests list between 2013-03-25 00:00:00 UTC and 2013-03-26 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]Still Failing - zopetoolkit_trunk - Build # 214 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 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 Still Failing - zopetoolkit_trunk - Build # 214 https://mail.zope.org/pipermail/zope-tests/2013-March/073549.html I can reproduce the problems. I do not understand at all, why buildout does not add persistent into the path for zope.traverser. Through dependency chains it depends on BTrees and BTrees depends on persistent, still, persistent is not in the paths for my script. Marius, can you show me your buildout script and your test script for zope traverser? Mine is: do3cc@BRICK cat bin/buildout | sed -e 's/\( *\).*\(\/[^\/]*\)\(\/[^\/]*\)/\1\2\3/' /bin/python import sys sys.path[0:0] = [ /eggs/distribute-0.6.35-py2.7.egg', /eggs/zc.buildout-2.0.1-py2.7.egg', ] import zc.buildout.buildout if __name__ == '__main__': sys.exit(zc.buildout.buildout.main()) do3cc@BRICK cat bin/test-ztk-zope.traversing | sed -e 's/\( *\).*\(\/[^\/]*\)\(\/[^\/]*\)/\1\2\3/' /bin/python import sys sys.path[0:0] = [ /zope.traversing/src', /zope.testrunner/src', /zope.interface/src', /zope.exceptions/src', /eggs/six-1.2.0-py2.7.egg', /eggs/distribute-0.6.35-py2.7.egg', /zope.testing/src', /zope.tales/src', /zope.security/src', /zope.configuration/src', /zope.component/src', /zope.browserresource/src', /zope.annotation/src', /zope.publisher/src', /zope.proxy/src', /zope.location/src', /zope.i18nmessageid/src', /zope.i18n/src', /src/transaction', /src/BTrees', /zope.schema/src', /zope.event/src', /zope.contenttype/src', /zope.browser/src', /eggs/pytz-2012j-py2.7.egg', ] import os sys.argv[0] = os.path.abspath(sys.argv[0]) /parts/test-ztk-zope.traversing') import zope.testrunner if __name__ == '__main__': sys.exit(zope.testrunner.run([ /zope.traversing/src', ])) I am using python 2.7 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 11, OK: 12
Am 07.03.2013 09:51 schrieb Marius Gedminas mar...@gedmin.as: On Thu, Mar 07, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 193 https://mail.zope.org/pipermail/zope-tests/2013-March/073094.html The usual ./bin/buildout -t 3 -v -c development-python.cfg failing because there's no development-python.cfg in SVN. There's a development-python2.cfg (rather new, added 3 days ago) and a development.cfg (which is older). Typo in the Jenkins job build steps? Its an easy to fix typo. Im just never in front of a real computer atm. [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.formui_py_265_32 [6]winbot / z3c.pagelet_py_265_32 [5]winbot / z3c.layer.ready2go_py_265_32 lxml [4]winbot / z3c.language.switch_py_265_32 Latest build is green! [7]winbot / zc.resourcelibrary_py_265_32 The usual weirdness with WindowsError. [8]winbot / zope.app.http_py_265_32 Hm, HEAD is now at 9df6d04 Pin zope.app.wsgi to 4.0dev to avoid test failures and then a failure in File c:\eggs\zope.app.wsgi-4.0.0a3-py2.6.egg\zope\app\wsgi\testlayer.py, line 21, in module so the pin didn't take effect. Huh? I see bin/buildout is version 1.7 on buildout, despite my replacing of bootstrap.py with the latest http://downloads.buildout.org/2/bootstrap.py. Why? The same fix worked for zope.app.publication somehow. Despite it also using zc.buildout 1.7, despite my latest bootstrap. Or did it? Nope, but that build happened four minutes after midnight and didn't make it into this build summary. Oh, right, the bootstrap step is c:\Python26_32\python.exe c:\buildmaster\bootstrap.py everything is clear now. (Including the fact that most packages I try to build locally fail because their bootstrap is too old. I was wondering why they didn't fail en-masse on winbot.) [9]winbot / zope.app.pagetemplate_py_265_32 [11] winbot / zope.browserpage_py_265_32 \r\n [10] winbot / zope.app.renderer_py_265_32 Renamed to zope.renderer. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-CMF] cmf-tests -
On Tue, Mar 5, 2013 at 12:05 AM, Hanno Schlichting ha...@hannosch.euwrote: Patrick Gerken patrick.gerken@... writes: are the missing CMF Tests only temporary or is there a need for a new source of test reports? I spoke to Stefan Holek and he no longer has the time nor interest to maintain the Zope2 and CMF nightly tests. He's not working on any web based projects anymore, so this is quite understandable. As CMF isn't moving to github, it seems the free travis-ci integration won't help here either. So if someone is interested in running the tests, that would probably be appreciated. I'll take care of it. ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] cmf-tests -
Hi , are the missing CMF Tests only temporary or is there a need for a new source of test reports? On Mon, Mar 4, 2013 at 2:00 AM, CMF tests summarizer nore...@zope.orgwrote: This is the summary for test reports received on the cmf-tests list between 2013-03-02 00:00:00 UTC and 2013-03-03 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 Non-OK results -- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-dev] zope-tests - FAILED: 21, OK: 15, UNKNOWN: 1
Hi, Both the daily zope app tests and the zope app tests that run with each commits have been deactivated. And Marius, thanks for dedication to look into the errors each day! Best regards, Patrick On Wed, Feb 27, 2013 at 8:21 AM, Marius Gedminas mar...@gedmin.as wrote: On Wed, Feb 27, 2013 at 08:55:21AM +0200, Marius Gedminas wrote: [3]Still Failing - zopetoolkit_trunk_app - Build # 167 Build #168: /tmp/hudson2996479762744665535.sh: 1: ./bin/test-zopeapp: not found Given http://zope3.pov.lt/trac/changeset/129871/zopetoolkit (aka remove all traces of zopeapp including test-zopeapp) this job should be disabled. [5]winbot / z3c.contents_py_265_32 [12] winbot / zope.app.authentication_py_265_32 [13] winbot / zope.app.authentication_py_265_32 [18] winbot / zope.ptresource_py_265_32 [19] winbot / zope.ptresource_py_265_32 Moved to github. These are already corrected in SVN. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 11, OK: 16
On Thu, Feb 14, 2013 at 8:28 AM, Marius Gedminas mar...@gedmin.as wrote: On Thu, Feb 14, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 171 https://mail.zope.org/pipermail/zope-tests/2013-February/072267.html Same zope.container error as yesterday. There's a Build # 172 as well, which fails curiously, while in buildout: While: Installing test-ztk. Getting distribution for 'zope.container'. Error: Picked: zope.container = 3.12.0 This error message never made sense to me. Maybe the buildout config (which I can't quickly check since it's password-protected in that Jenkins instance, annoying) has allow-picked-versions=false? I use the regular development.cfg. I just delete some test file, that's all about the specifics. development.cfg extends buildout, which in turn has this setting set. I am stumped too for now. All settings seem to be correct. Also, for completeness sake, my jenkins always starts a totally fresh buildout, there is no residue left behind. In other news, I added two more builders, they do not run every night, but with every commit to ztk. They are not as clean as the nightlies, they only delete the source directory before the builds. They also do not send mails to the mailing list. I'll add anybody who wants it to the notification list. Additionally, I'll create accounts for everybody who wants to help with tests on request. Tres and Marius got one already. Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 11, OK: 16
Hah, that zope.container problem wasn't all that hard after all. http://svn.zope.org/zopetoolkit/trunk/ztk-sources.cfg?rev=129373view=diffr1=129373r2=129372p1=zopetoolkit/trunk/ztk-sources.cfgp2=/zopetoolkit/trunk/ztk-sources.cfg On Thu, Feb 14, 2013 at 10:38 AM, Patrick Gerken do3cc...@googlemail.comwrote: On Thu, Feb 14, 2013 at 8:28 AM, Marius Gedminas mar...@gedmin.as wrote: On Thu, Feb 14, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 171 https://mail.zope.org/pipermail/zope-tests/2013-February/072267.html Same zope.container error as yesterday. There's a Build # 172 as well, which fails curiously, while in buildout: While: Installing test-ztk. Getting distribution for 'zope.container'. Error: Picked: zope.container = 3.12.0 This error message never made sense to me. Maybe the buildout config (which I can't quickly check since it's password-protected in that Jenkins instance, annoying) has allow-picked-versions=false? I use the regular development.cfg. I just delete some test file, that's all about the specifics. development.cfg extends buildout, which in turn has this setting set. I am stumped too for now. All settings seem to be correct. Also, for completeness sake, my jenkins always starts a totally fresh buildout, there is no residue left behind. In other news, I added two more builders, they do not run every night, but with every commit to ztk. They are not as clean as the nightlies, they only delete the source directory before the builds. They also do not send mails to the mailing list. I'll add anybody who wants it to the notification list. Additionally, I'll create accounts for everybody who wants to help with tests on request. Tres and Marius got one already. Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 5, OK: 23
ZTK will probably show an error on the next summary mail too, but my jenkins ran it successfully just now. On Thu, Feb 7, 2013 at 7:31 AM, Marius Gedminas mar...@gedmin.as wrote: On Thu, Feb 07, 2013 at 01:00:02AM +, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-02-05 00:00:00 UTC and 2013-02-06 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]Failure - zopetoolkit_trunk - Build # 163 [2]Failure - zopetoolkit_trunk_app - Build # 146 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_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 [3]winbot / z3c.recipe.paster_py_265_32 [4]winbot / z3c.recipe.paster_py_265_32 [5]winbot / zope.dottedname_py_265_32 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 Failure - zopetoolkit_trunk - Build # 163 https://mail.zope.org/pipermail/zope-tests/2013-February/071950.html [2]FAILED Failure - zopetoolkit_trunk_app - Build # 146 https://mail.zope.org/pipermail/zope-tests/2013-February/071951.html svn://svn.zope.org/repos/main/zopetoolkit/trunk needs to be told that zope.dottedname is now on github. (Done.) [5]FAILED winbot / zope.dottedname_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/071948.html The dreaded 24-hour lag: this build was still using svn. The next build succeeded. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Status of the buildout organization on github and a deleted branch
Hi, I thought I have was part of the buildout organization, but I am not now. I noticed because I wanted to recreate a branch that went missing. Could I either get commit access or could somebody recreate the 1.6.x branch. There is a buildout extension that breaks because of the missing branch. There seems to be no way to identify where exactly the branch was deleted, but the last mention of the branch is ef8c5e2a0d689e88e2a038f8346259e631956a1f Committed by Adam. I don't know if that was a merge that removed the branch or not, but as a starting point for a resurrected 1.6.x branch it seems bo ge good enough Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Status of github migration
Hi, I wanted to fix some logging in Products.SiteErrorLog, but I am confused where to go to. zopefoundation on github has a small number of repos but not Products.SiteErrorLog. http://svn.zope.org shows me a web view of our old cvs server. There is something wrong. Can I help with something? Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
Following your link it works for me too. Turned out I use a firefox plugin that if I enter a url without specifying a protocol, it tries https first. https://svn.zope.org redirects to the cvs. Regarding repos, I once did a full git mirror of the full svn.zope.org. I try to see if I can recreate single repos from it by moving stuff around and modifying the history. git svn clone is dog slow with svn.zope.org. On Thu, Jan 10, 2013 at 11:48 AM, Jens Vagelpohl j...@dataflake.org wrote: On Jan 10, 2013, at 11:23 , Patrick Gerken do3cc...@googlemail.com wrote: I wanted to fix some logging in Products.SiteErrorLog, but I am confused where to go to. zopefoundation on github has a small number of repos but not Products.SiteErrorLog. http://svn.zope.org shows me a web view of our old cvs server. There is something wrong. Can I help with something? Going to http://svn.zope.org works fine for me. I see the expected SVN repositories. The GitHub migration happens on an as-needed basis. Package maintainers may request to have packages migrated or, like Jim and Tres are already doing, migrate packages themselves. There is no full migration of all svn.zope.org content. For those packages that are fully migrated you will have obvious markers on the package in svn.zope.org, such as the package being read-only. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] How to signal that projects have moved to github
I am in favor of removing the trunks. People who do not want to switch to git can still get the trunk by pinning to a specific revision. I run a CI tool and it is broken already because apparently a trunk has been deleted already. Thats not a bug, thats why I run the CI Tool. Would be stupid if I continue to test a trunk not in use. Best regards, Patrick On Thu, Jan 10, 2013 at 3:15 PM, Jim Fulton j...@zope.com wrote: I'd like us to agree on how we're going to indicate in SVN that projects have been moved to github. Here's an opening bid: - Replace contents of trunk with a single file MOVED_TO_GITHUB containing the URL if the project page in github - Copy above file to root of project. - Make project read only An argument against cleaning out trunk will break CI tools. This is also an argument *for* cleaning out trunk. :) Thoughts? There are a lot of other details of the migration that need to be worked out, like how folks should request migration and automating the conversion further. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 5, OK: 19
[1]FAILED Still Failing - zopetoolkit_trunk - Build # 119 https://mail.zope.org/pipermail/zope-tests/2012-December/070665.html [2]FAILED Still Failing - zopetoolkit_trunk_app - Build # 103 https://mail.zope.org/pipermail/zope-tests/2012-December/070666.html This should stop failing now. I updated the svn:ignore properties in zope.security to fix it. [3]FAILED winbot / BTrees_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070686.html The tests only work with 64 bit. I only debugged code partially, but thats what I found: - a abs() method that does number = 0x7fff. I was able to replace that with sys.maxint to work on 32 bit - One test wanted to test for value errors on a method by providing sys.maxint + 1. The method used struct pack and unpack to ensure the variable is not too big. struct pack and unpack work with the same datasizes on 32 bit and 64 bit. I THINK the tests should be rewritten to use unpack to generate maxint, but I am not sure and hope somebody more knowledgeable than me can give his opinion here. [4]FAILED winbot / z3c.ptcompat_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070663.html Formatted output differs in whitespaces and newlines. z3c.ptcompat runs the test from zope.pagetemplates, the tests generate a different result than in zope.pagetemplates, because after z3c.ptcompat is installed, the renderer is chameleon. The tests that render differently in chameleon are new, thats why the tests fail even if nothing changed in z3c.ptcompat. It seems chameleon generates too many newlines for a tal repeat statement, in the output, it contains 2 newlines after each iteration. Does a chameleon developer read these mails and might want to comment? This is the input: !-- See https://bugs.launchpad.net/zope.pagetemplate/+bug/732972 -- ul metal:define-macro=tree li tal:content=context/name / li tal:repeat=context context/children ul metal:use-macro=template/macros/tree / /li /ul and this the output: !-- See https://bugs.launchpad.net/zope.pagetemplate/+bug/732972 -- ul liroot/li li ul lifirst/li /ul /li li ul lisecond/li /ul /li /ul [5]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070664.html The tests try to run a buildout in a fake root. I have the same problem under linux with python 2.7 64 bit. When I kill the test, go to the temp dir and run the buildout, all works fine, so this might be related to the fakeroot functionality from buildout. Maybe somebody who knows about that functionality of buildout could take a look? ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-CMF] Weird UnicodeDecodeError with zope.formlib
On Fri, Nov 30, 2012 at 11:19 AM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
Hi Patrick,
Am 30.11.2012, 09:50 Uhr, schrieb Patrick Gerken do3cc...@googlemail.com
:
Add sentry logging with raven to the sites. Trigger an exception in both
sites. With sentry you can not only see the traceback, but check the local
variable of each frame. You can do the same with pdb of course but not so
easily side by side to see where the local vars start to differ.
I can give you access to my sentry server to send the logs to.
thanks for the tip. I've got Sentry and Raven running and reporting but
I'm afraid I still can't see the difference. The posted form looks
indentical in both cases. I can only assume that, as you first suggested,
there is a difference lower down the stack which is causing one instance to
decode the URL-encoded form to unicode and the other to encode it as UTF-8.
How can I check this? locale.getdefaultlocale() reports ('de_DE', 'UTF8')
for both.
I don't understand why you see no difference in the stacktrace, but a
difference with pdb in the end. Doesn't one instance show that the input is
a string and the other that its unicode?
Do you see this until you extract it first from the request object?
You are not having one form saying fieldname:string and the other just
fieldname?
___
Zope-CMF maillist - Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Weird UnicodeDecodeError with zope.formlib
Did you try to put a pdb in prcessInputs of ZPublisher/HTTPRequest, around
line 642 where my code shows something like this:
640 if flags CONVERTED:
641 try:
642 if character_encoding:
643 # We have a string with a specified
character
644 # encoding. This gets passed to the
converter
645 # either as unicode, if it can handle
it, or
646 # crunched back down to latin-1 if it
can not.
647 item = unicode(item,character_encoding)
648 if
hasattr(converter,'convert_unicode'):
649 item =
converter.convert_unicode(item)
650 else:
651 item = converter(
652 item.encode(default_encoding))
653 else:
654 item = converter(item)
655
656 # Flag potentially unsafe values
657 if converter_type in ('string',
'required', 'text',
658 'ustring', 'utext'):
...
The only place I can see where a default encoding gets changed is by the
default-zpublisher-encoding from zope.conf
On Fri, Nov 30, 2012 at 6:14 PM, Patrick Gerken patrick.ger...@computer.org
wrote:
On Fri, Nov 30, 2012 at 11:19 AM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
Hi Patrick,
Am 30.11.2012, 09:50 Uhr, schrieb Patrick Gerken do3cc...@googlemail.com
:
Add sentry logging with raven to the sites. Trigger an exception in both
sites. With sentry you can not only see the traceback, but check the
local
variable of each frame. You can do the same with pdb of course but not so
easily side by side to see where the local vars start to differ.
I can give you access to my sentry server to send the logs to.
thanks for the tip. I've got Sentry and Raven running and reporting but
I'm afraid I still can't see the difference. The posted form looks
indentical in both cases. I can only assume that, as you first suggested,
there is a difference lower down the stack which is causing one instance to
decode the URL-encoded form to unicode and the other to encode it as UTF-8.
How can I check this? locale.getdefaultlocale() reports ('de_DE', 'UTF8')
for both.
I don't understand why you see no difference in the stacktrace, but a
difference with pdb in the end. Doesn't one instance show that the input is
a string and the other that its unicode?
Do you see this until you extract it first from the request object?
You are not having one form saying fieldname:string and the other just
fieldname?
___
Zope-CMF maillist - Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Weird UnicodeDecodeError with zope.formlib
With the information you provided I'd first try this on a python prompt on a working machine : Köln == uBonn If this does not throw the same error, somebody changed the python default encoding. Then I'd look if some of my validators get constraints with umlauts. But I guess, you tried that already? On Wed, Nov 28, 2012 at 7:12 PM, Charlie Clark charlie.cl...@clark-consulting.eu wrote: Hi, one of my sites has (hopefully) started behaving funny. I have a formlib driven contact form that is rejecting any input that is not ascii as part of the validation step of the form: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal I may have got this wrong but I thought inputs into forms could be considered as unicode and we only had to worry about them when storing them in case they were being accessed by non-unicode-aware code. What's really puzzling is that I have almost identical forms on other sites that don't exhibit this behaviour which makes me think it must be a configuration error such as the default encoding which is set to utf-8 for this site. Any ideas? Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 __**_ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/**listinfo/zope-cmfhttps://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/**zope-cmf/https://bugs.launchpad.net/zope-cmf/for bug reports and feature requests ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-dev] zope-tests - FAILED: 1, OK: 21
On Wed, Nov 21, 2012 at 2:00 AM, Zope tests summarizer nore...@zope.orgwrote: This is the summary for test reports received on the zope-tests list between 2012-11-19 00:00:00 UTC and 2012-11-20 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 # 82 Successful - zopetoolkit_trunk_app - Build # 66 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 [1]winbot / zc.lockfile_py_265_32 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 winbot / zc.lockfile_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-November/069449.html Some problem with mandatory file locking on windows. Could be a transient error. Else somebody might need to get into action on winbot. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 4, OK: 22
On Mon, Oct 29, 2012 at 2:00 AM, Zope tests summarizer nore...@zope.org wrote: Reports received ... Total languishing bugs for zope2: 0 HORRAY, zope2 is bugfree now! ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 2, OK: 21
On Tue, Oct 23, 2012 at 3:00 AM, Zope tests summarizer nore...@zope.org wrote: [1]Still Failing - zopetoolkit_trunk - Build # 51 [2]Still Failing - zopetoolkit_trunk_app - Build # 35 These bots have been fixed and don't fail any longer. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 8, OK: 18
On Mon, Oct 22, 2012 at 5:12 AM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/21/2012 09:00 PM, Zope tests summarizer wrote: [1]FAILED Failure - zopetoolkit_trunk - Build # 50 https://mail.zope.org/pipermail/zope-tests/2012-October/068769.html [2]FAILED Failure - zopetoolkit_trunk_app - Build # 34 https://mail.zope.org/pipermail/zope-tests/2012-October/068768.html These are both from a badly set-up Jenkins host (starzel.de): Spot on. I'm fixing it, in the mean time I deactivated notifications. There will be one more failure before that, unfortunately. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] unofficial svn mirror on github
Cool! There is btw a full repo copy under github at my user account, do3cc. Unfortunately a I dont push updates too often, but still a quick way to go through history Am 05.10.2012 10:21 schrieb johannes raggam raggam...@adm.at: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Zope Devs, because I want to do some research on the Zope source base (following commits, researching about the state of WSGI and the DateTime removal attempt in different branches, etc), I created a git clone of the Zope2 repository from svn.zope.org: $ git svn clone -s svn://svn.zope.org/repos/main/Zope It's really nice to browse through the commits, until the first one from 1996-06-17 by Jim Fulton Almost initial version., where Zope was only two modules: lib/python/ZPublisher/Publish.py and lib/python/ZPublisher/Response.py I uploaded it to github, so that others can also use it (The branches and tags have not been pushed yet): https://github.com/thet/Zope (See: https://github.com/thet/Zope/commits/master?page=342 for the beginning of History) I placed a note in the description, that the github repository is a unofficial mirror from svn.zope.org. I think about cloning even more relevant repositories from svn.zope.org, create a script to automatically sync it once per day and move it over to github, maybe a organisation called github.com/ZopeMirror What do you think about this? I know there is an ongoing discussion about moving to another SCM system or even using a SCM provider like github, bitbucket, gitorious, launchpad, ... I don't want to create any facts by creating a mirror - in fact, I'm not authorized to do anything without approval from the Zope Foundation. But I think a mirror on github would be just a nice thing to have, since their web interface is awesome. Best, Johannes Raggam - -- programmatic web development di(fh) johannes raggam / thet python plone zope development mail: off...@programmatic.pro web: http://programmatic.pro http://bluedynamics.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBumHUACgkQW4mNMQxDgAfdZwCgoIs4zYD1zhWUGeOpMRdasigt VFEAoLDVVYvjOtE1/mncwF7VlKywIwZk =3YCS -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - OK: 21
Thank you Adam for fixing the buildout errors! Best regards, Patrick On Wed, Oct 3, 2012 at 3:00 AM, Zope tests summarizer nore...@zope.org wrote: This is the summary for test reports received on the zope-tests list between 2012-10-01 00:00:00 UTC and 2012-10-02 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 # 31 Successful - zopetoolkit_trunk_app - Build # 15 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 -- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 6, OK: 19
On Fri, Sep 21, 2012 at 3:00 AM, Zope tests summarizer nore...@zope.org wrote: This is the summary for test reports received on the zope-tests list between 2012-09-19 00:00:00 UTC and 2012-09-20 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]Failure - zopetoolkit_trunk - Build # 19 [2]Failure - zopetoolkit_trunk_app - Build # 3 Transient network failures. I'll see if I find a clever way avoid triggering a build if there are network failures ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] QA
On Wed, Sep 12, 2012 at 5:37 PM, Adam GROSZER agros...@gmail.com wrote: Hello, I think I'm missing linux buildbots for our packages. ZTK itself seems to be well tested, but stand alone packages, most importantly trunks seem to have no public buildbots (or just I missed them?) At the moment all linux buildbots are already on 0.8.x and there seems to be an issue with sending mails, because none of the buildbots sends mails to the mailing list and nobody knows why. I have a running jenkins server again, I am not sure yet if this will stay on longtime, but I just added a test for zopetoolkit trunk with python2.7. It tests only the ztk packages for now. zope.component seems to be weird, the tests_standalone assume the zope packages to test are available for the used python interpreter which is not the case when using buildout. Any idea what is wrong here? Atm my setup deletes this file after checkout to avoid that test failure. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] QA
Oh wait: the jenkins is running under jenkins.starzel.de Best regards, Patrick On Thu, Sep 13, 2012 at 5:49 PM, Patrick Gerken do3cc...@googlemail.com wrote: On Wed, Sep 12, 2012 at 5:37 PM, Adam GROSZER agros...@gmail.com wrote: Hello, I think I'm missing linux buildbots for our packages. ZTK itself seems to be well tested, but stand alone packages, most importantly trunks seem to have no public buildbots (or just I missed them?) At the moment all linux buildbots are already on 0.8.x and there seems to be an issue with sending mails, because none of the buildbots sends mails to the mailing list and nobody knows why. I have a running jenkins server again, I am not sure yet if this will stay on longtime, but I just added a test for zopetoolkit trunk with python2.7. It tests only the ztk packages for now. zope.component seems to be weird, the tests_standalone assume the zope packages to test are available for the used python interpreter which is not the case when using buildout. Any idea what is wrong here? Atm my setup deletes this file after checkout to avoid that test failure. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-CMF] [dev] tools as utilities
On Thu, Sep 6, 2012 at 7:59 AM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/06/2012 01:37 AM, Lennart Regebro wrote: On Wed, Sep 5, 2012 at 5:01 PM, Tres Seaver tsea...@palladion.com wrote: And if we don't want to support more than one site the ZODB, there should be a warning of you try to do it, btw. I've got no problem with more than one CMF site in a single Zope instance; I just don't want to promote .zexp as the way to migrate such sites (that is what GS is for, after all). I'm confused now. GenericSetup has never been able to reliably export the content of a Plone site, to my knowledge. I'm sure we could make that happen, of course, but is that really less work than I have no idea what you man. GS has been the *only* means I have used for migrating CMF / Plone based sites for going on years now: I haven't used a .zexp export to do so in more than a decade (since well before GS was even released). Wait, what? Whenever I look into structure, there is only basic information, not even the workflow states of the objects get exported. What am I doing wrong? ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
[Zope-dev] Whats the right bugtracker for zc.relation?
Hi, I am having trouble with zc.relation and persistent token objects that I could not remove. I'd like to file a bug report, but it seems, there is no bug tracker for it, or is there? Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 29, OK: 15
Most of these tests seem to be real failures. I was wondering why they do only provoke errors on the winbots, this resulted in more questions. @Christophe Combelles @Marius Gedminas Both buildbots do not provide the xmlrpc interface any longer, do you know why? Did you maybe upgrade and this xmlrpc interface is not provided any longer? Also, we are currently only getting E-Mails from the winbots and Epy, so we only have windows tests and zope tests. No ztk or grok or bluebream for linux. Is this intentional, should I remove the buildbots from the documentation or just a mistake? On Sat, Aug 25, 2012 at 3:00 AM, Zope tests summarizer nore...@zope.org wrote: This is the summary for test reports received on the zope-tests list between 2012-08-23 00:00:00 UTC and 2012-08-24 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 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 [1]winbot / ZODB_dev py_265_win32 [2]winbot / ZODB_dev py_265_win64 [3]winbot / ZODB_dev py_270_win32 [4]winbot / ZODB_dev py_270_win64 [5]winbot / z3c.baseregistry_py_265_32 [6]winbot / z3c.contents_py_265_32 [7]winbot / z3c.contents_py_265_32 [8]winbot / z3c.coverage_py_265_32 [9]winbot / z3c.datagenerator_py_265_32 [10] winbot / z3c.formui_py_265_32 [11] winbot / z3c.layer.pagelet_py_265_32 [12] winbot / z3c.layer.ready2go_py_265_32 [13] winbot / z3c.menu.ready2go_py_265_32 [14] winbot / z3c.pagelet_py_265_32 [15] winbot / z3c.pdftemplate_py_265_32 [16] winbot / z3c.recipe.paster_py_265_32 [17] winbot / z3c.rml_py_265_32 [18] winbot / z3c.tabular_py_265_32 [19] winbot / z3c.tabular_py_265_32 [20] winbot / zc_buildout_dev py_254_win32 1.6.x [21] winbot / zc_buildout_dev py_265_win32 1.6.x [22] winbot / zc_buildout_dev py_265_win32 master [23] winbot / zc_buildout_dev py_265_win64 1.6.x [24] winbot / zc_buildout_dev py_265_win64 master [25] winbot / zc_buildout_dev py_270_win32 1.6.x [26] winbot / zc_buildout_dev py_270_win32 master [27] winbot / zc_buildout_dev py_270_win64 1.6.x [28] winbot / zc_buildout_dev py_270_win64 master [29] winbot / zope.app.twisted_py_265_32 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 winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2012-August/067180.html [2]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2012-August/067137.html [3]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2012-August/067138.html [4]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2012-August/067139.html [5]FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067140.html [6]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067162.html [7]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067142.html [8]FAILED winbot / z3c.coverage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067147.html [9]FAILED winbot / z3c.datagenerator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067151.html [10] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067153.html [11] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067150.html [12] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067145.html [13] FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067152.html [14] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067148.html [15] FAILED winbot / z3c.pdftemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067146.html [16] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067143.html [17]
Re: [Zope-dev] zope-tests - FAILED: 114, OK: 16
Looks like 1.6. buildout does not work well with windows. On Fri, Aug 17, 2012 at 3:00 AM, Zope tests summarizer nore...@zope.org wrote: This is the summary for test reports received on the zope-tests list between 2012-08-15 00:00:00 UTC and 2012-08-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 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 [1]winbot / ZODB_dev py_265_win32 [2]winbot / ZODB_dev py_265_win64 [3]winbot / ZODB_dev py_270_win32 [4]winbot / ZODB_dev py_270_win64 winbot / ZODB_dev py_270_win64 [5]winbot / z3c.form_py_265_32 [6]winbot / z3c.ptcompat_py_265_32 [7]winbot / zc.catalog_py_265_32 [8]winbot / zc.configuration_py_265_32 [9]winbot / zc.lockfile_py_265_32 [10] winbot / zc.monitor_py_265_32 [11] winbot / zc.ngi_py_265_32 [12] winbot / zc.queue_py_265_32 [13] winbot / zc.sourcefactory_py_265_32 [14] winbot / zc.table_py_265_32 [15] winbot / zope.annotation_py_265_32 [16] winbot / zope.app.applicationcontrol_py_265_32 [17] winbot / zope.app.appsetup_py_265_32 [18] winbot / zope.app.authentication_py_265_32 [19] winbot / zope.app.basicskin_py_265_32 [20] winbot / zope.app.broken_py_265_32 [21] winbot / zope.app.component_py_265_32 [22] winbot / zope.app.container_py_265_32 [23] winbot / zope.app.content_py_265_32 [24] winbot / zope.app.debug_py_265_32 [25] winbot / zope.app.dependable_py_265_32 [26] winbot / zope.app.error_py_265_32 [27] winbot / zope.app.exception_py_265_32 [28] winbot / zope.app.folder_py_265_32 [29] winbot / zope.app.form_py_265_32 [30] winbot / zope.app.generations_py_265_32 [31] winbot / zope.app.http_py_265_32 [32] winbot / zope.app.i18n_py_265_32 [33] winbot / zope.app.interface_py_265_32 [34] winbot / zope.app.locales_py_265_32 [35] winbot / zope.app.localpermission_py_265_32 [36] winbot / zope.app.pagetemplate_py_265_32 [37] winbot / zope.app.principalannotation_py_265_32 [38] winbot / zope.app.publication_py_265_32 [39] winbot / zope.app.publisher_py_265_32 [40] winbot / zope.app.renderer_py_265_32 [41] winbot / zope.app.rotterdam_py_265_32 [42] winbot / zope.app.schema_py_265_32 [43] winbot / zope.app.security_py_265_32 [44] winbot / zope.app.server_py_265_32 [45] winbot / zope.app.session_py_265_32 [46] winbot / zope.app.testing_py_265_32 [47] winbot / zope.app.wsgi_py_265_32 [48] winbot / zope.app.zcmlfiles_py_265_32 [49] winbot / zope.app.zopeappgenerations_py_265_32 [50] winbot / zope.applicationcontrol_py_265_32 [51] winbot / zope.authentication_py_265_32 [52] winbot / zope.browser_py_265_32 [53] winbot / zope.browsermenu_py_265_32 [54] winbot / zope.browserpage_py_265_32 [55] winbot / zope.browserresource_py_265_32 [56] winbot / zope.cachedescriptors_py_265_32 [57] winbot / zope.catalog_py_265_32 [58] winbot / zope.component_py_265_32 [59] winbot / zope.componentvocabulary_py_265_32 [60] winbot / zope.configuration_py_265_32 [61] winbot / zope.container_py_265_32 [62] winbot / zope.contentprovider_py_265_32 [63] winbot / zope.contenttype_py_265_32 [64] winbot / zope.copy_py_265_32 [65] winbot / zope.copypastemove_py_265_32 [66] winbot / zope.datetime_py_265_32 [67] winbot / zope.deferredimport_py_265_32 [68] winbot / zope.deprecation_py_265_32 [69] winbot / zope.dottedname_py_265_32 [70] winbot / zope.error_py_265_32 [71] winbot / zope.event_py_265_32 [72] winbot / zope.exceptions_py_265_32 [73] winbot / zope.filerepresentation_py_265_32 [74] winbot / zope.formlib_py_265_32 [75] winbot / zope.generations_py_265_32 [76] winbot / zope.hookable_py_265_32 [77] winbot / zope.i18n_py_265_32 [78] winbot / zope.i18nmessageid_py_265_32 [79] winbot / zope.index_py_265_32 [80] winbot / zope.interface_py_265_32 [81] winbot / zope.intid_py_265_32 [82] winbot / zope.keyreference_py_265_32 [83] winbot / zope.lifecycleevent_py_265_32 [84] winbot / zope.location_py_265_32 [85] winbot / zope.login_py_265_32 [86] winbot / zope.mimetype_py_265_32 [87] winbot / zope.minmax_py_265_32 [88] winbot / zope.pagetemplate_py_265_32 [89] winbot / zope.password_py_265_32 [90] winbot / zope.pluggableauth_py_265_32 [91] winbot / zope.principalannotation_py_265_32 [92] winbot / zope.principalregistry_py_265_32 [93] winbot / zope.processlifetime_py_265_32 [94] winbot / zope.proxy_py_265_32 [95] winbot / zope.ptresource_py_265_32
Re: [Zope-dev] zope-tests - FAILED: 11, OK: 23
On Wed, Jul 4, 2012 at 3:00 AM, Zope tests summarizer nore...@zope.org wrote: This is the summary for test reports received on the zope-tests list between 2012-07-02 00:00:00 UTC and 2012-07-03 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 Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-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 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 [1]winbot / zope.app.applicationcontrol_py_265_32 [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.component_py_265_32 [4]winbot / zope.app.container_py_265_32 [5]winbot / zope.app.exception_py_265_32 [6]winbot / zope.app.generations_py_265_32 [7]winbot / zope.app.publisher_py_265_32 [8]winbot / zope.app.rotterdam_py_265_32 [9]winbot / zope.app.session_py_265_32 [10] winbot / zope.app.testing_py_265_32 [11] winbot / zope.app.zcmlfiles_py_265_32 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 winbot / zope.app.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064994.html [2]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065004.html [3]FAILED winbot / zope.app.component_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064997.html [4]FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064996.html [5]FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065000.html [6]FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064992.html [7]FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065002.html [8]FAILED winbot / zope.app.rotterdam_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064995.html [9]FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065003.html [10] FAILED winbot / zope.app.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064998.html [11] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064999.html I didn't check ALL of the failures but the ones I checked all complayed that the layer attribute of browser:page is unknown. Apparently I still don't understand zcml enough, because I didn't find out, which package really provides this. There were some changes in zope.browserpage related to layers, but they aren't released as eggs yet and the test uses the eggified version of browser.page zope.publisher got a new release before the first failure, But I don't understand how this could affect the failure. Maybe somebody else here has an idea? ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 11, OK: 23
zope.component 4.0.0 and zope.browserpage 3.12.2 are not compatible. Tres, I think you made browserpage compatible on trunk, can you create a new release? Or anybody can add me as a package maintainer on pypi, I am do3cc. On Wed, Jul 4, 2012 at 11:05 AM, Patrick Gerken do3cc...@googlemail.com wrote: On Wed, Jul 4, 2012 at 3:00 AM, Zope tests summarizer nore...@zope.org wrote: This is the summary for test reports received on the zope-tests list between 2012-07-02 00:00:00 UTC and 2012-07-03 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 Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-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 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 [1]winbot / zope.app.applicationcontrol_py_265_32 [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.component_py_265_32 [4]winbot / zope.app.container_py_265_32 [5]winbot / zope.app.exception_py_265_32 [6]winbot / zope.app.generations_py_265_32 [7]winbot / zope.app.publisher_py_265_32 [8]winbot / zope.app.rotterdam_py_265_32 [9]winbot / zope.app.session_py_265_32 [10] winbot / zope.app.testing_py_265_32 [11] winbot / zope.app.zcmlfiles_py_265_32 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 winbot / zope.app.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064994.html [2]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065004.html [3]FAILED winbot / zope.app.component_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064997.html [4]FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064996.html [5]FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065000.html [6]FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064992.html [7]FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065002.html [8]FAILED winbot / zope.app.rotterdam_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064995.html [9]FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065003.html [10] FAILED winbot / zope.app.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064998.html [11] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064999.html I didn't check ALL of the failures but the ones I checked all complayed that the layer attribute of browser:page is unknown. Apparently I still don't understand zcml enough, because I didn't find out, which package really provides this. There were some changes in zope.browserpage related to layers, but they aren't released as eggs yet and the test uses the eggified version of browser.page zope.publisher got a new release before the first failure, But I don't understand how this could affect the failure. Maybe somebody else here has an idea? ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 3, OK: 38
On Tue, Jun 19, 2012 at 3:00 AM, Zope tests summarizer nore...@zope.org wrote: [1] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-June/064516.html [2] FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-June/064515.html The same well known bugs ass always :-( [3] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-June/064523.html Temporary network failure, works again. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4 release management
On Tue, Jun 12, 2012 at 2:50 PM, Jan-Carel Brand li...@opkode.com wrote: Do you also sync the git repo with new changes from the svn repo? Yes, but unfortunately 1. It takes ages 2. I have to do it on my laptop because none of my servers has enough inodes for that task. I do it once a day at the moment. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 6, OK: 40
On Mon, Jun 11, 2012 at 3:00 AM, Zope tests summarizer nore...@zope.org wrote: [1] FAILED Repository policy check found errors in 337 projects https://mail.zope.org/pipermail/zope-tests/2012-June/064183.html Is somebody working on this? [2] FAILED Total languishing bugs for zope: 62 https://mail.zope.org/pipermail/zope-tests/2012-June/064178.html [3] FAILED Total languishing bugs for zopeapp: 1 https://mail.zope.org/pipermail/zope-tests/2012-June/064175.html [4] FAILED Total languishing bugs for zopetoolkit: 209 https://mail.zope.org/pipermail/zope-tests/2012-June/064176.html I am not sure if these tests add any value the way it works now. [5] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-June/064182.html [6] FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-June/064180.html Just to be sure, I tried to reproduce the issues locally, and no surprise, no failure for me. Maybe a full cleanup of the sandbox might help. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4 release management
Hi, The ZF notes from May mentioned a VCS discussion. Is this the the latest thread or did I miss one more current for some reason? On Wed, Feb 1, 2012 at 3:40 PM, Alexandre Garel alex.ga...@tarentis.com wrote: Le 01/02/2012 14:21, Lennart Regebro a écrit : With dvcs everyone got full history of zope libs. I personally find it a big pro for a free software. While Lennart later rightly says, that svn also provides a full history, it is much slower. Even with the trac web interface that pov thankfully provides. Since I most often look for the history of something in SVN, I decided to finally make a git mirror for myself to quickly find the history of anything I might ever want. Since its for history only, I just imported the complete SVN repo as one git repo. So this is cannot be used as an alternative source for mr.developer. It is really only useful for history searching. Just for the case that somebody else might have an interest, I put it on github. Cloning will not make your harddisk explode, but you should have at least 750K Inodes available. A little vserver I used initially, did not have that many inodes. My dev machine has 6M Inodes (df -ih shows that) Even with the full svn history, looking up the full history of some file is superfast, with a regular hdd even. git status is something I woudn't do again, and updating the repo from svn is quite slow. If anybody is interested, the repo is here: https://github.com/do3cc/zope Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 5, OK: 37, UNKNOWN: 1
On Tue, May 22, 2012 at 3:00 AM, Zope tests summarizer nore...@zope.org wrote: [1] UNKNOWN FAILED (errors=1) : Zope-trunk-alltests Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2012-May/063362.html Bug in test code, looks like a refactoring went bad. Error in test test_EnsureProtectedDecoCall (AccessControl.tests.testClassSecurityInfo.ClassSecurityInfoTests) Traceback (most recent call last): File /usr/local/python2.6/lib/python2.6/unittest.py, line 279, in run testMethod() File /home/stefan/autotest/temp/python26-zope214all/eggs/AccessControl-3.0-py2.6-linux-x86_64.egg/AccessControl/tests/testClassSecurityInfo.py, line 131, in test_EnsureProtectedDecoCall with self.assertRaisesRegexp(AssertionError, 'has 2 non-decorator'): AttributeError: 'ClassSecurityInfoTests' object has no attribute 'assertRaisesRegexp' [2] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-May/063350.html [3] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-May/063352.html [4] FAILED ZTK 1.0dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-May/063351.html zope.app.twisted does not depend on twisted and does not have it as a dependency. [5] FAILED winbot / zope.app.appsetup_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/063340.html Same error as last time. Does it make sense to test zope.app.appsetup? ztk does not depend on it it is not part of zopeapp.cfg of ztk 1.1 Grok from 1.3 onward does not use it. Bluebream... Well, bluebream uses zopeapp 1.0, but its last release is also nearly 1.5 years ago. There seems to be a successor(?) named ztfy, which uses ztk 1.1 so is also not dependent on zope.app.appsetup. But I am not sure for how long already. Well, the question is, is there still a need for ztk 1.0 tests? If so, who are the consumers and for how long should we run the tests for 1.0? If anybody replies, please adjust the topic. I guess many people ignore the summarizer thread. [6] FAILED winbot / zope.configuration_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/063339.html Tres, could it be that this is related to the merge you did? ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZTK 1.0 lifetime
Eek, I started mixing up ztk and zope.app I didn't look too deep into Zope2 because my intention was more for asking whether packages like zope.app.appsetup need to be tested and they are only part of ztk 1.0 zopeapp.cfg, but now I had second look into versions.cfg of zope and plone and I am seeing that the latest plone still pins versions of ztk 1.0 zopeapp, and zope.app.appsetup even is a dependency somewhere in plone. Aww, too bad. Best regards, Patrick On Tue, May 22, 2012 at 4:57 PM, Hanno Schlichting ha...@hannosch.eu wrote: On Tue, May 22, 2012 at 4:32 AM, Patrick Gerken do3cc...@googlemail.com wrote: Well, the question is, is there still a need for ztk 1.0 tests? If so, who are the consumers and for how long should we run the tests for 1.0? Zope 2.13 is based on the ZTK 1.0. There's no version of Zope 2 that uses ZTK 1.1 and a potential Zope 4 is aiming at a future ZTK 1.2 (currently ZTK master). So from Zope 2's and Plone's perspective the ZTK 1.0 tests are vital and should be supported for the next couple of years. The only difference is that Zope 2 requires at least Python 2.6, so testing Python 2.5 + ZTK 1.0 isn't required. And this shouldn't be all too hard, as there's no major differences between ZTK 1.0 and 1.1. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 5, OK: 37, UNKNOWN: 1
On Tue, May 22, 2012 at 7:44 PM, Tres Seaver tsea...@palladion.com wrote: On 05/22/2012 04:32 AM, Patrick Gerken wrote: [2] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-May/063350.html [3] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-May/063352.html [4] FAILED ZTK 1.0dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-May/063351.html zope.app.twisted does not depend on twisted and does not have it as a dependency. I made a stab at fixing it, but couldn't figure out which version of Twisted was compatible (none of the more recent versions work). I have no idea why tests passed before I copied the release branch. [5] FAILED winbot / zope.app.appsetup_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/063340.html Same error as last time. Does it make sense to test zope.app.appsetup? ztk does not depend on it it is not part of zopeapp.cfg of ztk 1.1 Grok from 1.3 onward does not use it. Bluebream... Well, bluebream uses zopeapp 1.0, but its last release is also nearly 1.5 years ago. There seems to be a successor(?) named ztfy, which uses ztk 1.1 so is also not dependent on zope.app.appsetup. But I am not sure for how long already. Well, the question is, is there still a need for ztk 1.0 tests? If so, who are the consumers and for how long should we run the tests for 1.0? If anybody replies, please adjust the topic. I guess many people ignore the summarizer thread. I think we can safely stop testing the deprecated pacakgaes individually. Unfortunately somehow Plone still depends on it. [6] FAILED winbot / zope.configuration_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/063339.html Tres, could it be that this is related to the merge you did? This is a Windows-only failure which I have tried several times to whack. I THINK I fixed it. The commit message explains the failure if anybody wants to know. http://zope3.pov.lt/trac/changeset/126448 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 122, OK: 33, UNKNOWN: 2
Or maybe could another windows dev also provide support? Virtually everybody would know what to do with a failed linux build but with windows I am clueless. On Thu, May 10, 2012 at 6:49 PM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/09/2012 09:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2012-05-08 00:00:00 UTC and 2012-05-09 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 Can we please decomission the winbot until somebody has time to fix it? The false negatives could be masking real problems. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Design http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+r8ZwACgkQ+gerLs4ltQ6ogQCeMuCdh1bSPqelEO++m4Xtnhao fZsAoLH1GTjEIoKgZiufPQuWlXo74Anx =x10C -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 28, OK: 35, UNKNOWN: 2
All failures are because of import errors for zope.interface. Looking at some newer builds, the new failure is that pkg_resources are missing. Something seems to be seriously screwed up there. The two unknown build status are due to a timeout while trying to kill a process. I wish these builds would happen with Jenkins. With the right permission one can even see TTW whats in the working directory. On Sat, May 5, 2012 at 3:00 AM, Zope tests summarizer nore...@zope.org wrote: This is the summary for test reports received on the zope-tests list between 2012-05-03 00:00:00 UTC and 2012-05-04 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 Bluebream / Python2.5.5 64bit linux Bluebream / Python2.6.7 64bit linux Bluebream / Python2.7.2 64bit linux [1] UNKNOWN : winbot / ztk_dev py_265_win32 [2] UNKNOWN : winbot / ztk_dev py_265_win64 ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit ZTK 1.0dev / Python2.6.7 Linux 64bit ZTK 1.1 / Python2.5.5 Linux 64bit ZTK 1.1 / Python2.6.7 Linux 64bit ZTK 1.1 / Python2.7.2 Linux 64bit ZTK 1.1dev / Python2.5.5 Linux 64bit ZTK 1.1dev / Python2.6.7 Linux 64bit ZTK 1.1dev / Python2.7.2 Linux 64bit Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-2.13-alltests Python-2.6.6 : Linux Zope-trunk Python-2.6.6 : Linux Zope-trunk-alltests Python-2.6.6 : Linux winbot / ZODB_dev py_265_win32 [3] winbot / zc.resourcelibrary_py_265_32 [4] winbot / zc.table_py_265_32 [5] winbot / zope.app.appsetup_py_265_32 [6] winbot / zope.app.authentication_py_265_32 [7] winbot / zope.app.broken_py_265_32 [8] winbot / zope.app.dependable_py_265_32 [9] winbot / zope.app.interface_py_265_32 [10] winbot / zope.app.locales_py_265_32 [11] winbot / zope.app.localpermission_py_265_32 [12] winbot / zope.app.publisher_py_265_32 [13] winbot / zope.app.schema_py_265_32 [14] winbot / zope.app.session_py_265_32 [15] winbot / zope.app.wsgi_py_265_32 [16] winbot / zope.browsermenu_py_265_32 [17] winbot / zope.contenttype_py_265_32 [18] winbot / zope.datetime_py_265_32 [19] winbot / zope.event_py_265_32 [20] winbot / zope.interface_py_265_32 [21] winbot / zope.location_py_265_32 [22] winbot / zope.location_py_265_32 [23] winbot / zope.location_py_265_32 [24] winbot / zope.principalregistry_py_265_32 [25] winbot / zope.processlifetime_py_265_32 [26] winbot / zope.publisher_py_265_32 [27] winbot / zope.ramcache_py_265_32 [28] winbot / zope.sendmail_py_265_32 [29] winbot / zope.size_py_265_32 [30] winbot / zope.traversing_py_265_32 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 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -- [1] UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2012-May/061607.html [2] UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2012-May/061608.html [3] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/061573.html [4] FAILED winbot / zc.table_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/061570.html [5] FAILED winbot / zope.app.appsetup_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/061564.html [6] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/061582.html [7] FAILED winbot / zope.app.broken_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/061568.html [8] FAILED winbot / zope.app.dependable_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/061560.html [9] FAILED winbot / zope.app.interface_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/061579.html [10] FAILED winbot / zope.app.locales_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-May/061572.html [11] FAILED winbot /
Re: [Zope-dev] zope-tests - OK: 34, UNKNOWN: 6
On Fri, Apr 27, 2012 at 03:00, Zope tests summarizer nore...@zope.org wrote: [1] UNKNOWN UNKNOWN : Zope-2.13 Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2012-April/061065.html [2] UNKNOWN UNKNOWN : Zope-2.13-alltests Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2012-April/061066.html [3] UNKNOWN UNKNOWN : Zope-trunk Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2012-April/061067.html [4] UNKNOWN UNKNOWN : Zope-trunk-alltests Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2012-April/061068.html I am not sure about these, either network failures or something is happening on the servers, I hope the errors will be gone next run. [5] UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2012-April/061069.html [6] UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2012-April/061070.html There still seem to be processes hanging on the windows boxes, unfortunately. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - OK: 38, UNKNOWN: 2
On Tue, Apr 24, 2012 at 03:00, Zope tests summarizer nore...@zope.org wrote: Non-OK results -- [1] UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2012-April/060949.html [2] UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2012-April/060950.html There seems to be a permission problem on the windows server itself. exceptions.WindowsError: [Error 5] Access is denied: 'c:\\buildslave\\ztk_dev_py_265_win64\\build\\bin\\test-zopeapp-zc.sourcefactory.exe' Hannosch, could this be related to your cleanup? ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 1, OK: 40
On Wed, Apr 4, 2012 at 03:00, Zope tests summarizer nore...@zope.org wrote: Non-OK results -- [1] FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-April/060115.html Seemed to be a strange one time error. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bugtracker for z3c.relationfield and reasons for objects loosing their parent pointers
Hi, I found out, somewhat surprised, that __parent__ pointers are just disguised aq_parent pointers. The changelog entries for zope 2.12 are a bit misleading in this regard. Is there somewhere an explanation of how this works? I was quite by some of the properties. Best regards, Patrick On Tue, Mar 27, 2012 at 00:09, Patrick Gerken do3cc...@googlemail.com wrote: Hi, I have a very curious problem with relationfields, and I don't know which bugtracker to use for z3c.relationfield. So, hopefully somebody here can give me some pointers. The relations are persistent objects and the from relation is stored directly on them on the from_object. For some reason, the existing relations have from objects without __parent__ or aq_parent pointers. When I update a relation, from_object is updated with an object with __parent__ and aq_parent pointers. After restart, the pointers are gone, the attribute value is None. When I want to delete the relation target object, Plone first starts a savepoint, tries to delete the object, catches any exceptions and does a rollback. It does so to test for certain exception. After the rollback, the objects lost their __parent__ and aq_parent pointers. There was something else that felt odd. the object in from_object always returned a string representation without a path on obj.__str__(), but a string representation with a path when doing obj.__repr__() and when the object had __parent__ pointers. I noticed that, because print statements and pdb tests displayed different things. The whole thing happens in Zope 2.13 with dexterity content types. I have no idea why this could happen. Anybody has any pointers for me? Thanks and best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bugtracker for z3c.relationfield and reasons for objects loosing their parent pointers
Hi, I have a very curious problem with relationfields, and I don't know which bugtracker to use for z3c.relationfield. So, hopefully somebody here can give me some pointers. The relations are persistent objects and the from relation is stored directly on them on the from_object. For some reason, the existing relations have from objects without __parent__ or aq_parent pointers. When I update a relation, from_object is updated with an object with __parent__ and aq_parent pointers. After restart, the pointers are gone, the attribute value is None. When I want to delete the relation target object, Plone first starts a savepoint, tries to delete the object, catches any exceptions and does a rollback. It does so to test for certain exception. After the rollback, the objects lost their __parent__ and aq_parent pointers. There was something else that felt odd. the object in from_object always returned a string representation without a path on obj.__str__(), but a string representation with a path when doing obj.__repr__() and when the object had __parent__ pointers. I noticed that, because print statements and pdb tests displayed different things. The whole thing happens in Zope 2.13 with dexterity content types. I have no idea why this could happen. Anybody has any pointers for me? Thanks and best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 1, OK: 45
On Fri, Nov 25, 2011 at 02:00, Zope tests summarizer nore...@zope.org wrote: Non-OK results -- [1] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-November/053119.html Hi, regarding the network time outs happening a lot lately. I am a bit out of the loop whats possible with buildbot, but I've seen a solution for this issue in the jenkins builders for Plone. They have a build that just checks out code. The actual tests are then run as a dependant build, but only if the checkout of step one worked. The builds are independent, so the code actually gets checked out twice. But the nice effect is, that we wouldn't get false errors because of network issues. Any of our buildbot admins sees this as feasable and might share his configuration of how to do it? Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-CMF] cmf-tests - OK: 2, UNKNOWN: 2
On Wed, Nov 23, 2011 at 02:00, CMF tests summarizer nore...@zope.org wrote: This is the summary for test reports received on the cmf-tests list between 2011-11-21 00:00:00 UTC and 2011-11-22 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 CMF-2.2 Zope-2.12 Python-2.6.6 : Linux CMF-2.2 Zope-2.13 Python-2.6.6 : Linux [1] FAILED (errors=3) : CMF-trunk Zope-2.13 Python-2.6.6 : Linux [2] FAILED (errors=3) : CMF-trunk Zope-trunk Python-2.6.6 : Linux Both failures should be fixed. Regarding the changes itself, while Products.GenericSetup 1.7.0dev will not play well with released Packages of Products.DCWorkflow, the changed Products.DCWorkflow will work with GS 1.6. Best regards, Patrick ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
[Zope-dev] Version number policy if default values change
Hi, GenericSetup wasn't very good in handling non ascii chars on exporting. I changed the behavior so that it will only dump strings to files/zodb/tgzs and modified the provided exporters to default encode text as utf-8. Since this breaks packages, I'd increase the minor number from 1.6 to 1.7. To get a plone system to work with these changes, I needed to update Products.DCWorkflow, Products.PluggableAuthService and Products.PluginRegistry. Since in all these packages I only changed the default encoding from None to utf-8 I wonder if this requires a higher minor number or not. I'd say no, as anything that was just stored as ascii, would be properly decoded as utf-8 too. So before I change the numbers and ask for new release, I'd like to ask if anybody objects. Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[ZWeb] www.zope.org accounts for submitting ssh keys
Hi, I initially failed to submit a new ssh key for commit access, because I didn't remember my password on the old zope.org site. Tres helpfully reminded me that I can still access the old zope.org on old.zope.org. I updated the developer docs for new developers who want to become submitter, but I wonder if it should stay this way that people have to use old.zope.org to register their username and password to be able to submit their ssh key on cvs.zope.org. Best regards, Patrick ___ Zope-web maillist - Zope-web@zope.org https://mail.zope.org/mailman/listinfo/zope-web
Re: [Zope-dev] Zope Tests: 42 OK, 8 Failed
On Thu, Oct 7, 2010 at 10:50, Wichert Akkerman wich...@wiggy.net wrote: On 10/7/10 08:52 , Jens Vagelpohl wrote: For me personally the value has dropped so far that I am mostly ignoring those emails. They are hard to parse to begin with and there are just too many buildbot entries. Likewise. I've redirected all test-mails to /dev/null for a long time. Which projects do you not want to see in this summary mail? Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 42 OK, 8 Failed
On Thu, Oct 7, 2010 at 11:28, Wichert Akkerman wich...@wiggy.net wrote: On 10/7/10 11:26 , Hanno Schlichting wrote: +1 for a brief summary, the direct links to the build results are still important though and should be somewhere in the mail Please don't forget we also have a page that links to all buildbots and display latest status too. http://docs.zope.org/zopetoolkit/process/buildbots.html Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] buildbots should have an svn info step
On Wed, Sep 22, 2010 at 00:54, Marius Gedminas mar...@gedmin.as wrote: On Tue, Sep 21, 2010 at 04:33:35PM +0200, Adam GROSZER wrote: Hello Patrick, Could you nag the buildbot maintainers to add an svn info step for their bots? The issue is that you can get the svn URL only from the bot config, which is not always available. Patrick asked me a while ago to switch to using mode='clobber', which means the initial checkout step always does an rm -rf followed by an svn checkout with the full URL. Yes, but some rightfully objected that creates lots of traffic. I think it would be nice if everybody sweeps their slaves contents once in a while, like weekly. I also really like the svn info step. I have seen ccomb has something a bit more advanced, but I have to check that again. Apart from that, I think it was your idea, that everybody should try to trigger their buildbots at the same time, like midnight GMT. That sounds also good. Next week I will go through the current buildbot list and collect some more information, and contact each one individually. This week I won't find the time. Best regards, Patrick Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkyZN4YACgkQkVdEXeem14/m4ACePID0XyNjE8oWd+LwxAjACQg1 dZ8An3m61AwCgwkdlUk+m2yGW4p2h01t =5+MJ -END PGP SIGNATURE- ___ Zope-Dev maillist - zope-...@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) signature.asc Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Survey: most obscure errors
Hi It doesn't happen to me any longer, cause I learned my lesson, but in the beginning I was always confused about the error message when an exception happened in the __init__ method of a view. The Exception gets caught, and interpreted as if the object object/view does not exist. I then always checked if I made a mistake in my zcml declaration or did something wrong with names. It never occured to me that the url was correct, but the __init__ method threw errors. Best regards, Patrick On Tue, Sep 14, 2010 at 12:00, Marius Gedminas mar...@gedmin.as wrote: What are the most obscure error conditions you've encountered while developing Zopeish[1] applications? [1] ZTK, Grok, Bluebream, the old Zope 3.x KGSes all qualify. I'm talking about situations where the error message/traceback are disconnected from the actual cause. For example, forgetting to add a security declaration in ZCML can cause TraversalError (because ForbiddenAttribute is a subclass of AttributeError), which leads the developer off to a wild goose chase looking for why the attribute is missing (was it misspelled? did it come from an old database?) the first few times this kind of error happens. One of the goals we came up with in the Zope Summit in Halle was to identify the most annoying of these kinds of error messages and fix them. I need your help for the identifying part! Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkyPR7UACgkQkVdEXeem14+KfQCdEk2D4poDir5CKqL+0+svjHRV YWsAnjndhGiLGatmmjje08lcj2pYkCyE =XE/L -END PGP SIGNATURE- ___ Zope-Dev maillist - zope-...@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 46 OK, 7 Failed, 2 Unknown
I believe, nobody had yet the chance to change the configuration to follow the branch. that buildbot still follows the trunk. Best regards, Patrick On Thu, Sep 16, 2010 at 13:12, Michael Howitz m...@gocept.com wrote: Am 15.09.2010 um 13:58 schrieb Zope Tests Summarizer: [...] Test failures - [...] Subject: FAILED : ZTK 1.0 / Python2.4.6 Linux 64bit From: ccomb at free.fr Date: Wed Sep 15 01:26:59 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020028.html Which SVN-URL does this buildbout use for buildout? Sorry, I did not find any hint in the buildbot UI. Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - zope-...@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 31 OK, 19 Failed, 2 Unknown
Hmm, thats a lot of new failures. And after homing in http://dev.thehealthagency.com/buildbot/builders/zope2%20slave-ubuntu64/builds/345 http://dev.thehealthagency.com/buildbot/builders/zope2%20slave-ubuntu64/builds/344 I made out this changeset http://zope3.pov.lt/trac/changeset/116291 as the culprit. The change was done after a discussion about lxml on the very same mailing list. Essentially, understanding what fails and fixing it without pinning lxml back to 2.2.6 would help the people working on windows. So, any takers from the windows camp who can tackle the issue? Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 46 OK, 21 Failed, 1 Unknown
On Wed, Aug 25, 2010 at 14:45, Marius Gedminas mar...@gedmin.as wrote: On Wed, Aug 25, 2010 at 01:59:18PM +0200, Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Tue Aug 24 12:00:00 2010 UTC to Wed Aug 25 12:00:00 2010 UTC. There were 68 messages: ... 14 from buildbot at pov.lt, Is there a way to tell buildbot to *not* send emails when build reason is someone pushed a button on the web page (while trying to fix a failed build)? Of those 14 messages only the last 4 are relevant (and they all passed). I' rather have a look into the script and see if I can limit the report to only report the last build per day. Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] vocabularies missing wihtout zope.app.schema
On Mon, Jan 11, 2010 at 17:52, Hanno Schlichting ha...@hannosch.eu wrote: On Mon, Jan 11, 2010 at 4:31 PM, Roger d...@projekt01.ch wrote: The zope.componentvocabulary package defines some basic vocabulary (factory) classes. Probably we should move the zope/app/schema/vocabulary.py to this package as registry.py. If it doesn't introduce new dependencies, that sounds good. Hi, with the newest plone4 beta there is an empty vocabulary registry because no package imports zope.app.schema any longer. I am not sure if the registry from zope.app.schema belongs to zope.componentvocabulary. After all zope.componentvocabulary provides vocabularies for components while zope.app.schema replaces the current, non component based registry with his own one. How about moving the code into zope.schema and make it the default registry if zope.component is available? Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Which bugtracker to use for z3c.formwidget
Hi, the question says it all, what bugtracker is currently used for the formwidgets? I have an issue with z3c.formwidget.query and created a branch with a fix. But before asking for a new release I wanted somebody to look over it. The branch is svn://svn.zope.org/repos/main/z3c.formwidget.query/branches/do3cc_dont_fail_on_missing_terms Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope] long running methods
On Thu, May 20, 2010 at 14:18, Jürgen Herrmann juergen.herrm...@xlhost.dewrote: hi there! as our zope2 zodb grows we experience more and more conflicts with long running transactions. so i'm going to rewrite these methods to commit transactions in batches - here my attempt to tackle this problem. the idea is to get a list of objects to be modified in this transaction, break it down to batches and commit after each batch was processed. to avoid zope's retry-on-conflict machinery and still have a chance to retry per batch transaction commits, the iteration over one batch is guarded by a try:except ConflictError: and a retry logic. Zope already has its own retry mechanism, maybe you might want to call your long running method multiple times, each time working on the next batch. Viele Grüße, Patrick ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-dev] Repository for the zope mail summarizer
Hi, I wanted to look into the script that summarizes the mails sent to zope-test. The best code I found is this http://cvs.zope.org/Packages/TestScripts/ but I suspect that there are newer versions, I just don't know where. I'd like modifiy the script to understand status mails from buildbots too. Anybody knows where the latest version of this code is? And who runs that script atm? Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Update on ztk kgs: Python 2.6 issues
Yes, I would say so. This http://zope3.pov.lt/trac/browser/zope.testing/trunk/src/zope/testing/testrunner/profiling.py#L86 Was never an official feature, also I did not see an obvious alternative http://www.python.org/doc/2.4.4/lib/profile-stats.html Apart from that, hotshot is now unmaintained and might be removed http://www.python.org/doc/2.6.2/library/hotshot.html We still have the cProfile Profiler. It seems that hotshots focus was on faster profiling, but I don't see an issue here, since nobody runs a profiler in his production environments. Best regards, Patrick On Tue, Sep 15, 2009 at 21:21, Jim Fulton j...@zope.com wrote: On Tue, Sep 15, 2009 at 12:08 PM, Patrick Gerken do3cc...@googlemail.com wrote: Hi, I have removed that profiler for python2.6 My understanding of the python api is, that we were using an undocumented feature to merge two hotshot profiler results. Since nobody maintains hotshot any longer, there probably won't be anybody adding this feature officially. Tests on 2.6 work for me now. Thanks. That's probably the right first step. Does this mean we're permanently removing this feature? That would be OK with me. Jim -- Jim Fulton ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Broken Objects in BtreeFolder
Hi, we had all kinds of funny behaviour that all was rooted in a bad object in a BTreeFolder. When calling folder.objectIds() I get the id of the object in question, when I call folder[object_id] I get a Key Error. Stepping into the code with the debugger, it looked like the Tree stores the objects in a dict grouped by type. I found out, that the objects in question all were of a type that is not available in the portal, and should not. So I added the product with the code for the type and restarted, but I still could not access the objects in question. The object can not be deleted. I managed to solve the worst problem, by creating a new object in that folder with the same id. Now only this new object can be reached, but the old object is still there, cause the object count, shown in the zmi, increased by one. Also, deleting this new object with the same id brings back the old object with the same id. I am out of ideas how to clean up the database. I also don't know how this happened in the first place. Therefore I can not provide a description of how to reproduce the problem. I am more interested atm how to clean up the screwed up zodb. How can I really get rid of the object? Best regards, Patrick ___ 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] REQUEST vs. request
Hi, thank you for all that answers, this was really helpful! On Mon, Jun 22, 2009 at 12:18, Hanno Schlichting ha...@hannosch.eu wrote: On Tue, Jun 16, 2009 at 10:35 PM, Patrick Gerkendo3cc...@googlemail.com wrote: A testcase in my code fails, and after a lot of digging, I am finding that the reason are wrong results from the catalog. The catalog returns bad results because he caches the results in the request. My test consists of a number of steps, for multiple times I do a getMultiAdapter, always with fresh TestRequests. Still it seems, that the catalog always use some other, rotten REQUEST. Looking at this again, you are missing an important point about the test framework you use. In all of ZopeTestCase (CMFTestCase, PloneTestCase) you get a convenience request object set up for you, reachable as app.REQUEST. This mirrors the way you usually get access to the request object in Zope2 via Acquisition down to the application root. It's meant to emulate a very minimal request object. Now in normal operation, you would get one request object per HTTP request. This also works in the functional variants of the test case classes. In the non-functional test classes you only ever get one request object set up, as there's no object publishing or HTTP request handling being done. If you or any code you call changes any settings on that request object and you want to test things dependent on this you have two options: Either create a fresh request yourself (using Testing.makerequest) in your tests or use a functional test case instead. I did excactly that. Since it was a caching issue in code out of my reach, I had problems with. Sadly, creating a new request and saving it on self.app.REQUEST was not enough. The code in question acquires the method that caches something on the REQUEST from a getSite() call. It seems like getSite() returns a copy of the site, and that has its own copy of the request too. self.app.REQUEST == getSite().REQUEST True self.app = makerequest(self.app) self.app.REQUEST == getSite().REQUEST False The copy getSite() returns is deleted in an EndRequest Event handler... I did not use zc.testbrowser for testing, because I did test XMLRPC Methods, and it seemed easier to just use getMultiAdapter and test the view directly. I solved my issues but it is a bit inconvenient nowadays... Best regards and thank you! Patrick ___ 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 )
[Zope-dev] REQUEST vs. request
Hello, I am a bit confused about self.request and self.REQUEST. Can anybody point me to an explanation of the different tasks that both have? Googling for request vs REQUEST is not helpful... Here is the reason why I am wondering: Context is a small product to be used in plone. A testcase in my code fails, and after a lot of digging, I am finding that the reason are wrong results from the catalog. The catalog returns bad results because he caches the results in the request. My test consists of a number of steps, for multiple times I do a getMultiAdapter, always with fresh TestRequests. Still it seems, that the catalog always use some other, rotten REQUEST. When stepping through, I see this happening: 1. my BrowserView calls something like self.context.portal_catalog(kw) There is no request as an argument 2. The method I call wants that as a positional argument, but has None as the default value That None value gets passed on. 3. In Products.ZCatalog.Catalog:searchResults the code checks whether the REQUEST variable is None, and if so, retrieves self.REQUEST. self.REQUEST ist the rotten REQUEST, self.request would still be available 4. Total chaos is ensured I can imagine more than one way to fix it, but I don't understand the difference and reasoning sufficiently to decide, what would be the right(tm) way to fix it. Any points will be really appreciated! Best regards, Patrick ___ 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] Installing Zope 3
On Tue, May 26, 2009 at 17:25, Michael Haubenwallner mich...@d2m.at wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan Ulrich Hasecke wrote: I think that http://www.zope.org/Products/ should be updated. No chance for a newbie to find http://wiki.zope.org/zope3/Zope3Wiki I do not know how you think the 2 pages should be related but - The Relation is, that one expects to find the link to the newest Zope3 on http://www.zope.org/Products/ but that http://wiki.zope.org/zope3/Zope3Wiki provides it. The more important aspect of the mail is, that the Products page is outdated, and it would be cool if somebody with write access could update it. Best regards, Patrick ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-dev] ZTK futures: one big package?
On Wed, May 13, 2009 at 16:23, Martijn Faassen faas...@startifact.comwrote: I start being scared of using pypi. Why? Because I can imagine case where I would like to remove a package. I did just that in a totally unrelated piece of software where I wrote an extension. After a while I realized, that another extension was not all that different, so I refactored the other extension and now it contains my features as a configuration option. I was just made clear, that this might not work very well in pypi. Scared is a very strong word for what I intended to say. I do not want to abuse you here as a support forum for pypi, but would it be possible to publish a new release, but without providing the distribution files? The intention would be, not the break the installations with pinned versions, but breaking attempts to get the newest versions, because the distribution files would be missing. The people might then check the webpage of pypi, where the readme would state that the package has been discontinued and can be found in package x.y. As a next step, pypi might offer some way to ignore these packages in searches. If this would work, it could be a way to reduce packages over time (Provided the dependency reduction shows that they don't need a live on their own). Best regards, Patrick ___ 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] ZTK futures: one big package?
On Wed, May 13, 2009 at 15:29, Martijn Faassen faas...@startifact.comwrote: Chris McDonough wrote: We can ameliorate the situation in a few ways: - We can reduce the number of distributions. - We can make each current Zope package distribution independently useful. My suggestion is that we do the former first in order to communicate *current intent* (the state of reality right now). We can do the latter after this in pieces, hopefully aided by some new developers we've picked up by making it easier to find useful stuff. In order for your plan to work I think you'd need two things ideally: * remove a lot of the released packages from pypi. This is a no-go. People depend on these in a massive way. Wouldn't it be possible to put them on a dedicated pypi? pypi.support.zope.com? I start being scared of using pypi. Best regards, Patrick ___ 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] ZTK futures: one big package?
Hi, I agree with the package inflation. It makes people nervous of the complexity. But putting everything back into a pile of mud sounds like going back from where we came, and I this situation makes people even more nervous when they want to look into zope. As far as I know, the big dependency clean up is not finished yet, no? Maybe it might be better to do that first. With a clean dependency graph, its easier to see, which set of packages could be merged into one package. About the configurability of all the subpackages, I remember a proposal long time ago to reduce the number of zcml directives. This time I am in favor of inventing some zcml directives with some care. But before doing that, it might be better to write two or free easy tutorials about how to write custom zcml directives and grokkers. That would result in people writing more custom zcml directives and grokkers and get the hang of it. With the a much bigger userbase of writers of custom zcml directives and grokkers, the community as a whole will get a much better idea of how to use zcml, and I think gaining that community sense first will result in some high quality new general usable zcml directives. At the moment, and with my limited view, it looks like most zope ppl really don't know how to write custom zcml directives. Just my 0.02€ Best regards, Patrick On Tue, May 12, 2009 at 09:08, Chris McDonough chr...@plope.com wrote: I realize now that I've neglected to give sufficient reasoning for why less granular packaging would be a good thing. I've noticed that there's a common theme in Zope development, software, and packages that I can only describe as power law development or turtles all the way down. It's a bit of an antipattern, unfortunately. I'll provide an example by way of Zope-3-the-appserver. In an application that uses Zope-3-the-appserver, many individual subframeworks will be used. For example, there is a traversal subframework, a security subframework, a cataloging subframework, and so on. Each of these subframeworks acts as a logical unit, and through the magic of the component architecture, each can be replaced wholesale by registering some adapter. However, each of these subframeworks tend to also have settings that can be configured. For example, individual traversal steps for certain types of objects can be overridden by registering an adapter that *configures* the subframework. In the case of Zope 3, we have a traversal situation where the larger traversal subframework can either be replaced wholesale via an adapter registration or extended piecemeal via other adapter registrations. The problem is that the mechanism to *replace* the subframework is the same as the mechanism to *configure* it (both are done via adapter registration, sometimes even in the same file). This is theoretically fine. But in reality, it's tremendously hard for someone just walking up to a complex system like Zope 3 to discern adapter registrations that replace subsystems from those which merely configure subsystems. An inability to discern the difference leads to situations where people just don't get the joke and try to wiggle wires to configure-to-death a existing subsystem that's clearly suboptimal for their use case instead of just replacing it wholesale with a much simpler custom policy. They just don't know it was engineered to be replaced. So they keep adding more configuration code to the existing subframework to handle various 1% edge cases. Often this code makes the subframework tremendously complex, and the subframework grows inappropriate dependencies along the way. *Sometimes* the situation gets so confusing for a new user, they just quit and go use something else. This is a pattern that happens over and over again in Zope development. In my personal opinion, the original error was trying to make the subframework configurable at all. Instead, the subframework should be replaceable easily, but it should itself be relatively rigid. At very least, for subframeworks that really do require extra configuration (should be very few), this configuration should be done via highly specialized ZCML directives (or grokkers), as opposed to some very general adapter registration that can't be easily discerned from other adapter registrations by a newbie. If the subframeworks were more rigid (but replaceable), the *intent* of the subframework author could be more easily discerned, and fewer people would fall into the trap of adding more configuration code to a subframework instead of just replacing it entirely. And fewer people would just walk away in frustration. What does this have to do with packaging? Well, currently, there's a dizzying number of packages that make up the ZTK (nee Zope 3). Each of these packages is a pure peer of all others in a PyPI listing with no real way to get a sense of their relative importance other
Re: [Zope] Fwd: Building a fast, scalable yet small Zope application
On Sun, Apr 26, 2009 at 19:45, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Patrick Gerken wrote: Argl, why does this mailing list not use the reply-to: field? That would be a religious question, and one which is not helpful to debate here.. E.g., see: http://www.unicom.com/pw/reply-to-harmful.html Thank you for that explanation. That makes sense. Best regards, Patrick ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Fwd: Building a fast, scalable yet small Zope application
Argl, why does this mailing list not use the reply-to: field? -- Forwarded message -- From: Patrick Gerken do3cc...@googlemail.com Date: Sat, Apr 25, 2009 at 15:43 Subject: Re: [Zope] Building a fast, scalable yet small Zope application To: Morten W. Petersen mor...@nidelven-it.no On Sat, Apr 25, 2009 at 13:24, Morten W. Petersen mor...@nidelven-it.no wrote: Hi, I'm considering building a large scale, but small in features site. It will contain lots of small objects (millions, tens of millions, hundreds of millions) of objects, where each object has a couple of strings and maybe some other light attributes. So far, I've been contemplating disabling undo (if that's possible), and using BTree structures, maybe segmenting objects into different groups (folders) to further speed up lookups. Scalability is also an issue, should I consider using RelStorage? Should I consider using the ZCatalog for faster lookups? Has anyone else developed something similar? Are there Zope product examples out there that fit the bill? Hi, I once was involved in developing a system that supposedly should be able to handle a very big number of objects. They chose to put all the base objects into mysql too, and use mysql for object lookup. I do not know what type of benchmarks they did to conclude that this was the best choice. But they regulary did queries for which relational databases were made. If your data contains lots of small items, that are all similar of content, and you want to do queries that involves many of these attributes, you might want to take a look at orm tools. relstorage will not help you with your queries, because it stores everything as a pickle, afaik. I suggest you experiment a bit. Create 100 million objects, and do some of the actions you are planning to do on them. Best regards, Patrick ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-dev] Fwd: Defining Zope 3.
Hi, I usually love gmail, but in these last discussions I have trouble to understand, where I should write my reply to, since I can not see a thread. So I write a reply to the first mail and reference to various mails below. Sorry for that confusion to the people who use real mail readers! I would like to comment on this stuff with a bit of an outsider view. Somewhere in 2005-2006 I got a bit disconnected from zope and its evolvement. I was stuck to, I think, 2.8, and lots of Zope2 specialities that exist in Zope2 and not in Zope3. I disliked the things that were in Zope2 but not in Zope3. I must admit, that's a bit of fan boy attitude that I must get rid of. But in the time 2005, 2006, Z3 was the new kid on the block, everybody was wondering who would need how much time to migrate to the new zope. Zope3 was the big rewrite that will be the standard soon. Now I was told that Zope3 is not being seen as a replacement of Zope2. That stuck me as odd. Philips book does not say, that Zope3 will replace Zope2. But he suggests to try to use as much Zope3 technology through five, to have an easy migration. That at least suggests that Zope3 is the future while Zope2 is not. When I go to www.zope.org and click on Zope 3 on the left, I reach a wiki page that states that Zope 3 improves the development experience. There is nowhere written that Zope3 replaces Zope2. But it also suggests it. The English entry of the wikipedia states clearly that Zope3 is not the successor, an older version even points to suggestions from Jim, where is a discussion about the possible future: http://mail.zope.org/pipermail/zope3-dev/2006-February/018415.html I did not check wikipedia, nor did I skim the last three years of mailing list traffic, I wonder, did I not do enough thoroughly research in 2008? = I came back to Zope Land in October 2008. I became responsible for a number of web apps that are based on Zope2, all programming logic in Script Python, and all data in MySQL. Actually even security was implemented on its own based on attributes in sql. I considered this an outdated development model. But I am beginning to understand that this is wrong, that's my damn fan boy attitude. Everybody said, Zope3 is better so Zope2 models that were not taken over clearly must suck. Funnily, I tend to gravitate to products that handle zope2 development this way. 2005/2006 I was also doing stuff, there all I did was considered customization and should be handled in script python. The developers went big ways to make this better and better, they even added svn support for the scripts! But I disliked it, fan boy that I am, and was thinking: Hah, when Zope3 comes along and Zope2 will be outdated, they must rethink their strategy, then they see that this has no future. I disregarded the business decisions these companies made with the way they did Zope development and considered it inferior. But these companies have based their development model on this. They allow customers who do customizations in code, and depend on Zope, to take care that their customers cant break their system. This is their competitive advantage that they cant afford to loose. That is a different culture and mind than the ones who do typical Zope3 development. For the Zope3 developer, the only ones who program are the programmers and keeping the code in file system and unrestricted is much much better because you have all the development tools at hand to have higher productivity and safety. Think versioning system and easy search and replace over multiple files. With this in mind, Zope2 and Zope3 are totally different things. People who use Zope2 and want to continue using it have different goals than the Zope3 developers. I think, both have the right to have their own communities. A different name would help separating these communities. People who do both Zope2 and Zope3 stuff would just be in two communities. = When I started big extensions in October 2008, I wanted to do it future proof, Zope3ey. I knew of grok, thought of it as something on top of Zope3 and repoze, that seemed to be something different altogether. I wanted to do a smooth migration. As much as possible should be written on top of the Zope3 part in Zope2, so that one day I would just run it on Zope3 directly. I didn't want to use grok, because I feared it would add another complication, and I wanted to do one new thing at a time. It didn't work out exactly like that. Stumbling and stumbling but finally succeeding I ended up reimplementing nearly everything. My goal still was to get it all going on Zope3 one day, but I stayed with Zope 2.10. Now after reading the threads, I start to believe that this was the wrong way. I think now grok is not so much on top of Zope3, and maybe I should have taken a deeper look into that. But how shall somebody, who does not wade through the
Re: [Zope] Zope pretends to receive and send XMLRPC data, but strace sees nothing !
On 1/18/07, yacine chaouche [EMAIL PROTECTED] wrote:
Hi,
I have an ajax application that is composed by :
1) An ajax client which is a web page with a button that calls a zope
object's method, say toutCompter.
2) An ajax server (zope), with a zope object that has the method
toutCompter (all zope object methods are XMLRPC callable right ?).
I use two browsers on two separate machines. I call the methode on the two
browsers, and compares the zope trace and strace output of the network
activity. The problem is that zope says he sends data but strace don't, and
zope says he receives data and again strace don't.
This is the zope/python code that prints to the console :
zope/python
def toutCompter(self):
this method is called via XMLRPC.
IPAdresse = self.REQUEST[REMOTE_ADDR]
print ip:,IPAdresse,requests counting of lines,self.getForm
('min'),to,self.getForm('max')
... #some processing here. creation of XMLData
print sending results to +IPAdresse
return XMLData
/zope/python
Zope says :
zope traces to the console
ip: 10.75.49.155 requests counting of lines 10 to 20
ip: 10.75.49.51 requests counting of lines 10 to 20
sending results to 10.75.49.155
sending results to 10.75.49.51
ip: 10.75.49.51 requests counting of lines 10 to 20
sending results to 10.75.49.51
/zope trace
instead of strace try tcpdump, much more helpful:
tcpdump -i INTERFACE -s 0 -A HOST HOST AND PORT PORT
should show the reality
Best regards,
Patrick
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-dev] SOAP support?
On 1/7/07, Andreas Jung [EMAIL PROTECTED] wrote: Hi, I think it would be time to support SOAP out-of-the-box in some way in Zope 2. XMLRPC is still a useful functionality but the whole world speak of web-services and Zope should support building web-services at least on the SOAP level. I am sure that would bring back some more attention to Zope as application-server. There are several SOAP related products available on zope.org. Does anyone know about their functionality, pros cons? I know that there is also some SOAP support available for Plone/Archetypes (I think written by Benjamin Saller). Thoughts? We implemented a soap service one year ago, in the end, I was parsing the incoming stream, and generated the soap messages by hand. The available tools at that time were soappy with a zope2 wrapper and zsi 2.0 soappy was already in a stage where the developers said that they dont maintain it any more, and people should use zsi. At that time zsi was mostly dead, but some people were writing, there would be a new version soon. That actually happened, but I never looked into that 2.0 version, because I could read and write soap requests already. The old zsi looked very complicated, and threw errors at my wsdl spec. A bit off topic but I still want to throw it in: If you have the freedom to decide whether you offer soap services or not, please read these texts during your evaluation: http://wanderingbarque.com/nonintersecting/2006/11/15/the-s-stands-for-simple/ http://www.somebits.com/weblog/tech/bad/whySoapSucks.html Especially the strong typing bites us hard sometimes. If I had to support a soap interface as a server, I would receive a wsdl spec file, and would have to implement the message stubs, so for this part, I would need a wsdl parser that creates method stubs. If I would be a client, I would receive a wsdl spec file and would need a wsdl parser that creates method stubs, that actually make type checks of what I send. In the real worlds I live in, it would not help to make every method automatically available as a soap service, because there are ugly and subtle impendance mismatches, for example, if you would want to transfer sets instead of lists. It would be serious pita, to write a method so that it adheres to a complex, given wsdl spec file, and that is probably most often the case. So maybe, soap support would just mean a good documentation of integration of zsi generated code in your product code. Best regards, Patrick Gerken ___ 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] Wrapping zope with socksify
On 12/17/06, Dieter Maurer [EMAIL PROTECTED] wrote: Patrick Gerken wrote at 2006-12-13 16:13 +0100: ... Now we got the problem that zope randomly crashed. There are many ways crashed can be interpreted. If crashed means died from a fatal signal (SIGSEGV, SIGBUS, SIGABORT, ...), then the analysis of the core file may provide valuable insights. I am sometimes really bad in answering to helpful tipps :-( The last look at it with strace showed that I should not try to debug this thing by using threads. I still dont know the exact signal he emits, but I know now that it is a problem independent of zope, the same access in pure python code now crashes too now and then. We will first try to upgrade to newer versions of python and then see again. Best regards, Patrick Gerken -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Wrapping zope with socksify
Hello, we wanted to open connections from within zope to other elements. As the other elements require that we connect to them via a socks server, we considered it a good idea to wrap zope with socksify. socksify is a program from the dante package which allows you to add socks support for any network application by just wrapping the application with socksify. It is just like using strace on linux. Now we got the problem that zope randomly crashed. We suspected that the socksify version we used was faulty and tried it with the latest socksify version as a static compiled binary, but had similar problems. Did somebody else try to wrap zope with socksify and had success with it? I found only this hint that application developers should take care of: *select(2)/poll(2)*applications combining non-blocking sockets with select(2)/poll(2) need to make sure they can handle the select(2)/poll(2) call being interrupted. This is due to how the Dante clientlibrary implements support for non-blocking connect(2).But our application crashed randomly, and not when we tried to access certain ftp servers. Best regards, Patrick Gerken ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Fwd: XML export/import is cool! (Was Re: [Zope-dev] Deprecating XML export/import?)]
On 10/27/06, Lennart Regebro [EMAIL PROTECTED] wrote: It has not worked for a long time, and that's because not many peopleuse it. But those who do usually uses it a lot, so it would be bad ifit goes away.I would propose that somone that uses this heavily (like the Nexedi people), joins the Zope Foundation as a commiter, gets commiter rightsand holds his or her hands over this functionality. :)He, thats odd, just yesterday at a local zope meeting, a friend mentioned that he knows a company that does the same thing quite regulary. Maybe they can be forces joined in getting it right in the zope core again!And if they could write some unittests that would be even better. :) --Lennart Regebro, Nuxeo http://www.nuxeo.com/CPS Content Management http://www.nuxeo.org/___ Zope-Dev maillist-Zope-Dev@zope.orghttp://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 ) ___ 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] Re: Future of ZClasses
Above all, I should mention that I believe this discussion is largely about Z3, and I do not live in Z3 world yet. Actually I am developing more in 2.7 currently. But the policy I state below is valid for 2.x also, afaik. On 10/4/06, Jean-Marc Orliaguet [EMAIL PROTECTED] wrote: Patrick Gerken wrote: I think we use Interfaces in Z3 to publish Methods. So maybe it makes sense to have a smaller core API with longer deprecation periods, so that standard projects can try to rely on core API with long deprecation phase and extender would use the one year deprecation phase. But as I said earlier, I think we are quite ahead already. I guess the motivation of this API stability discussion is also motivated by JMOs comment about how much more stable is the Java API, in Point 2 and 3 of this entry: Everyone deprecates stuff, this is not the question. But what is marked as 'stable', 'official' or 'standard' may not be deprecated in the same way as something that is still under development or private. It is more a question of defining and maintaining a contract with API users than a question of technicalities (how often to deprecate, what version numbers to use, how to inform...) This is all about defining and maintaining a social contract with the user. No one prevents you from deprecating parts of an API that is marked as being under development or private -- as long as you say it from the start. Check out for instance: http://openide.netbeans.org/tutorial/api-design.html especially the chapter Life-cycle of an API I can see no guarantee for a time line What is unclear in zope is what is official, what is stable, what is still under development, etc. It seems that all the different packages have the same status, or rather that they have no status. Apart from the packages that were added recently (zc. ...) there is no information in the repository about the quality of the different APIs. There are no version numbers on the packages either so I don't know what is alpha, beta, or final. It gives the impression that the framework is stable, but not mature. I'd expect that the API defined in the 'interfaces.py' files for instance are 'official' in the sense that there is a commitment that the API is ready and that it won't change until the next major version, but I doubt that this is understood by everyone putting stuff into these files. Deprecation can happen at any time. Anything deprecated in one release will create deprecation warnings when used for two major releases. After that the code is removed. That is the official policy. Though I believe this was never mentioned explicitly, this policy relates to the releases packaged by Andreas and Philip. So for any code released in these packages this policy is used. I BELIEVE, this is also true for all other packages on svn.zope.org Through it is unclear, which of these have stable releases. I would say that everything just in svn is unstable, and stable is, what is in the zope core packages or on cheeseshop. in Java, you can mark a class as 'final', meaning that no one will be able to subclass it, or methods can be marked as 'private'. Abstract classes can specify the methods that must be implemented. Also if a class says that it implements an interface it has to implement it otherwise the code won't compile. So here I must admit that I am from Zope2 world mostly, but some smaller Z3 code I checked actually hat assertions in their code (not in the tests directory), that checks whether its own objects really obey the interface. This is worse than in Java but shows that at least these developers were aware of these things. Sadly, except for using Meta classes I see no way to make these checks implicit like they are in Java. This is a language problem. Again this is all about defining contracts. Considering the standard JBoss modules, there is no way to compare with zope really since they strive to implement the specifications thoroughly (EJB3, JSR-168, ...) and the APIs are final already, so they don't change. Well, I can only answer with accusations like they influence the standards so much that you could already say they define the standard, and about the API I could ask how the react to changing environments, but that would not be fair, since I did not research the accusations nor how stable the API really is and what the API defines. Maybe somebody with better background can put these accusations on solid ground until then I have to believe Jean-Marc here. Anyway I appreciate your critics Jean-Marc. best regards, Patrick ___ 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] Re: Future of ZClasses
On 10/2/06, Olavo Santos [EMAIL PROTECTED] wrote: Just a quick side note. Many deprecation sign for any user are clearly signs that Zope developers are unable to maintain certain Zope features. This is bad, specially for guys that have to manage large, complex and long time running zope installations ( think years ). And a no sir, next app! for guys like us who have to choose opensource development platforms for the long run ( again: think years ). Well, though nothing is perfect in Zope world, I think we are quite good in having a policy about deprecation which already gives a guaranteed timelime for deprecation. I wanted to find a deprecation policy for eclipse and JBoss to compare. For JBoss i did not find such a thing, for eclipse I did not find a eclipse framework one, but one for some sub projects: http://www.eclipse.org/webtools/adopters/#non-api-code-deprecation-policy and somehow this popped up in the eclipse search result: http://maven.apache.org/development/deprecation.html Notice especially how they mention that a deprecation phase can be days. So for me it looks we are actually a bit ahead of the competition, but maybe somebody can correct me. Accidently I lately tripped over an article from Martin Fowler about this topic: http://www.martinfowler.com/ieeeSoftware/published.pdf I think we use Interfaces in Z3 to publish Methods. So maybe it makes sense to have a smaller core API with longer deprecation periods, so that standard projects can try to rely on core API with long deprecation phase and extender would use the one year deprecation phase. But as I said earlier, I think we are quite ahead already. I guess the motivation of this API stability discussion is also motivated by JMOs comment about how much more stable is the Java API, in Point 2 and 3 of this entry: http://www.z3lab.org/sections/blogs/jean-marc-orliaguet/2006_09_23_times-they-changin But it is not fair to compare the stability of a programming language standard modules API with a application framework api. But maybe I am not good in searching and somebody points me to the well thought out JBoss or Websphere deprecation policy best regards, Patrick ___ 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 )
[Zope-dev] HTMLFile vs DTMLFile
Hello, looking through old bugs, I saw one about some issue with HTMLFile. I started to wonder, why would want somebody to use HTLMFile, if DTMLFile exists, and DTMLFile, allows you to define your own global namespace, what HTMLFile doesn't According to this thread http://marc.theaimsgroup.com/?l=zope-devm=100160092618036w=2 The basic difference is that DTMLFile does some mangling with the global namespace that HTMLFile doesn't, thus making HTMLFile a bit more dangerous. Might HTMLFile be a candidate for deprecation? best regards, Patrick Gerken ___ 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 )
[Zope-dev] Fwd: [Zope3-dev] The bug fixing problem
Forwarded as a discussion starting point about bug fixing problems (If I understood Jim correctly) -- Forwarded message -- From: Jim Fulton [EMAIL PROTECTED] Date: Sep 11, 2006 4:09 PM Subject: Re: [Zope3-dev] The bug fixing problem To: Patrick Gerken [EMAIL PROTECTED] Cc: zope3-dev@zope.org On Sep 11, 2006, at 5:47 AM, Patrick Gerken wrote: On 7/16/06, Jim Fulton [EMAIL PROTECTED] wrote: On Jul 11, 2006, at 8:05 AM, Patrick Gerken wrote: On 7/7/06, Julien Anguenot [EMAIL PROTECTED] wrote: ... I marked the bug as bug + bugfix but nobody cares. That is much more discouraging than what I can not do nice wiki links to in my bugreport other bugtracker items or svn sources like it is possible in trac itself. What is the issue number you are referring to? I don't see any bug+solution issues that seem to be from you. Perhaps you submitted 572? Or perhaps your issue was resolved. Sorry for the very late answer, but our employee put us into a tourist place with no internet access, and before I sent the link I wanted to ensure that the tests still work. This is the issue: http://www.zope.org/Collectors/Zope/1944 Hm, That is the Zope collector not the Zope 3 collector. That's why I didn't see it. Perhaps you could bring this on on the zope-dev list. But the original issue is just, that it turns one off, to see no response, of course I'm giving a bad example in responding so late. You are giving a very realistic example. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ 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 )
[Zope-dev] ConflictError shouldn't subclass Exception
2005/11/24, Chris Withers [EMAIL PROTECTED]: Interestingly, you can raise things that don't subclass Exception in python. This was discussed before, and I firmly agree with, that zodb conflicts should _not_ sublcass exception. That way, there's less chance of them being caught by inexperienced programmers putting in try: except Exception: 's. How would we go about making this change? class my_own_exception: pass try: raise my_own_exception() except: print Doesn't help against inexperienced programmers. sadly You can even raise a string, which is accidently done in zope2 and where my with provided solution and unit test is pending. It is better to beat people using except: without good reasons. Patrick ___ 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] Re: Timing the opening of network ports
2005/11/12, Florent Guillaume [EMAIL PROTECTED]: +1 on the general goals, however I have no idea if it's easy to implement. Does this sound reasonable to make the behaviour of opening the ports configurable? Does anybody have an idea how hard this would be to do? I was curious and tried it. Sadly the patches are against 2.7.8, but the patches itself are relative small and should be easy to apply. I did not write unittests. I just wanted to invest 5 minutes to see how it can be done, and suddenly could not stop finishing it. If somebody reminds me of it in two or three weeks, I will make patches against current with unit tests. I am not happy with how I implemented the listening delay. patching the listen method to only listen when the configuration says fast_listen is not good. but otherwise I would have to patch the medusa sources itself. If this is feasible I can do it, is medusa maintained here or in another project? To configure it, add a fast_listen False to the http-server section in your config. Patrick ZServer_HTTPServer.py.patch Description: Binary data ZServer_component.xml.patch Description: Binary data ZServer_datatypes.py.patch Description: Binary data Zope_Startup___init__py.patch Description: Binary data ___ 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 )
