Re: [Zope-dev] zope-tests - FAILED: 6, OK: 17
On Sat, Dec 1, 2012 at 8:00 PM, Zope tests summarizer nore...@zope.org wrote: ... [1]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2012-December/069693.html [2]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2012-December/069694.html [3]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2012-December/069695.html [4]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2012-December/069696.html This is due to the release yesterday. I can and will fix this, by providing a test extra, but this will only cause no tests to run. The fix may be needed for test of third-party packages that depend on ZODB3 [test]. The winbot needs to be modified to run the tests for persistent, BTrees, ZODB and ZEO separately. [5]FAILED winbot / zc.lockfile_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/069675.html I'll look at this today. 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 )
Re: [Zope-dev] [Zope-CMF] Weird UnicodeDecodeError with zope.formlib
Am 30.11.2012, 18:21 Uhr, schrieb Charlie Clark
charlie.cl...@clark-consulting.eu:
Let me explain: in pdb I have access to request.form which is where I
can see the difference. With Sentry I can only see the raw body of the
request. I may simply have not understood well enough how to use it to
inspect what's happening.
I raise an exception in both cases in the forms' validate method.
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?
No, they are all zope.formlib/zope.schema fields so there is no
additional marshalling.
I have finally tracked down the problem: I seem to have been bitten by a
change in zope.formlib 4.1.
There are two solutions: either extend a form's update method with the
something like the following:
def update(self):
from Products.Five.browser.decode import processInputs
from ZPublisher import HTTPRequest
# XXX: if we don't set default_encoding explicitly, main_template
might
# set a different charset
self.request.RESPONSE.setHeader('Content-Type',
'text/html; charset=%s' % HTTPRequest.default_encoding)
# BBB: for Zope 2.14
if not getattr(self.request, 'postProcessInputs', False):
processInputs(self.request, [HTTPRequest.default_encoding])
super(_EditFormMixin, self).update()
Or, more simply, base forms on those provided by five.formlib.formbase
Thanks to yuppie for fixing this in the CMF.
I can confirm that this also works with Internet Explorer.
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-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: 17
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/02/2012 08:55 AM, Jim Fulton wrote: On Sat, Dec 1, 2012 at 8:00 PM, Zope tests summarizer nore...@zope.org wrote: ... [1]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2012-December/069693.html [2]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2012-December/069694.html [3]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2012-December/069695.html [4]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2012-December/069696.html This is due to the release yesterday. I can and will fix this, by providing a test extra, but this will only cause no tests to run. The fix may be needed for test of third-party packages that depend on ZODB3 [test]. The winbot needs to be modified to run the tests for persistent, BTrees, ZODB and ZEO separately. [5]FAILED winbot / zc.lockfile_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/069675.html I'll look at this today. If ZODB3 no longer has tests (as a pure meta-package), then dropping the 'test' dependency and changing the buldout.cfg accordingly seems correct. If you want to allow thrid-party pacakges to use the '[test]' extra, you could have it depend on the corresponding extras (if any) for the underlying real packages. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlC7gpIACgkQ+gerLs4ltQ7tEQCfRxFDioiJ51o+WWnZIh05daxv 5ZgAn04Xe61mG8TVbW26agkfYroBf5Ng =8Uhh -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 )
Re: [Zope-dev] zope-tests - FAILED: 6, OK: 17
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/02/2012 11:32 AM, Tres Seaver wrote: If ZODB3 no longer has tests (as a pure meta-package), then dropping the 'test' dependency and changing the buldout.cfg accordingly seems correct. If you want to allow thrid-party pacakges to use the '[test]' extra, you could have it depend on the corresponding extras (if any) for the underlying real packages. Oops, I missed seeing that you had already done the latter. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlC7gzcACgkQ+gerLs4ltQ4+pgCfVa9dX45r+4R9VAwArOPLYcOV 7nIAn3aJ6RbHZvSYmSg5jahDiBaOv7q/ =8PQR -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 )
Re: [Zope-dev] zope-tests - FAILED: 6, OK: 17
On Sun, Dec 2, 2012 at 11:32 AM, Tres Seaver tsea...@palladion.com wrote: ... If ZODB3 no longer has tests (as a pure meta-package), then dropping the 'test' dependency and changing the buldout.cfg accordingly seems correct. If you want to allow thrid-party pacakges to use the '[test]' extra, you could have it depend on the corresponding extras (if any) for the underlying real packages. Yup, in the long run, bit in the short run, I don't want to break packages that depend on ZODB3 [test]. I released a2 which ads back this extra. 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] zope-tests - FAILED: 8, OK: 21
This is the summary for test reports received on the zope-tests list between 2012-12-01 00:00:00 UTC and 2012-12-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 [1]Repository policy check found errors in 277 projects Successful - zopetoolkit_trunk - Build # 94 Successful - zopetoolkit_trunk_app - Build # 78 [2]Total languishing bugs for zope2: 4 [3]Total languishing bugs for zope: 72 [4]Total languishing bugs for zopeapp: 1 [5]Total languishing bugs for zopetoolkit: 207 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 [6]winbot / z3c.recipe.paster_py_265_32 [7]winbot / zc.lockfile_py_265_32 [8]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 Repository policy check found errors in 277 projects https://mail.zope.org/pipermail/zope-tests/2012-December/069704.html [2]FAILED Total languishing bugs for zope2: 4 https://mail.zope.org/pipermail/zope-tests/2012-December/069703.html [3]FAILED Total languishing bugs for zope: 72 https://mail.zope.org/pipermail/zope-tests/2012-December/069702.html [4]FAILED Total languishing bugs for zopeapp: 1 https://mail.zope.org/pipermail/zope-tests/2012-December/069700.html [5]FAILED Total languishing bugs for zopetoolkit: 207 https://mail.zope.org/pipermail/zope-tests/2012-December/069701.html [6]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/069699.html [7]FAILED winbot / zc.lockfile_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/069714.html [8]FAILED winbot / zc.lockfile_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/069698.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 )
