Hi, we've recently seen a the Data.fs in a few of our Zope systems grow
rather fat (from stable sizes around the 100-300MB level to 3GB in the
most extreme cases).
On further investigation it appears that regular user page requests are
being recorded in the Zope undo log - these are not object
On 06.05.09 12:36, John Snowdon wrote:
but can anyone shed any light on the possible
issues that would cause regular requests to be logged in this way?
This is nothing but a wild guess.
There are utilities under utilities/ZODBTools within the Zope source
tree for performing low-level analysis
On Wed, May 6, 2009 at 12:36, John Snowdon j.p.snow...@newcastle.ac.uk wrote:
Systems are all 2.11.0 Zope clients with Data.fs served by matching
versions of Zeo. Not all of our 2.11.0 apps that are showing this
behaviour, only a couple, so I doubt it's something wrong with Zope or
ZEO.
Yeah,
On Wed, May 6, 2009 16:17, Chris Withers wrote:
Jürgen Herrmann wrote:
2.Script Python instances don't execute anymore. not the ones already in
the db from the zope 2.10 install i used before nor newly created ones.
traceback:
Yes they do ;-)
* Module ZPublisher.Publish, line
On Wed, May 6, 2009 16:16, Chris Withers wrote:
Jürgen Herrmann wrote:
1. standard_error_message is not used, this is due to code in
ZPublisher/HTTPResponse.py, method _error_html(self,title,body) comment:
XXX could this try
to use standard_error_message somehow?
The code you're
On Wed, May 6, 2009 16:16, Chris Withers wrote:
Jürgen Herrmann wrote:
1. standard_error_message is not used, this is due to code in
ZPublisher/HTTPResponse.py, method _error_html(self,title,body) comment:
XXX could this try
to use standard_error_message somehow?
The code you're
Shane Hathaway wrote:
Jürgen Herrmann wrote:
ZConfig.SchemaResourceError: import name does not refer to a package
Package name: 'relstorage'
File name: 'component.xml'
Package path: None
I need to make a new release of RelStorage before this will work.
RelStorage 1.1.3 does not
Log message for revision 99791:
Break out logic for converting string name to exception type.
Changed:
U Zope/trunk/src/zExceptions/__init__.py
A Zope/trunk/src/zExceptions/tests/test___init__.py
-=-
Modified: Zope/trunk/src/zExceptions/__init__.py
Log message for revision 99792:
LP #372629: fix dtml-raise for zExceptions.
Changed:
U Zope/trunk/src/DocumentTemplate/DT_Raise.py
A Zope/trunk/src/DocumentTemplate/tests/test_DT_Raise.py
-=-
Modified: Zope/trunk/src/DocumentTemplate/DT_Raise.py
Log message for revision 99793:
Note work on LP 372629.
Changed:
U Zope/trunk/doc/CHANGES.rst
-=-
Modified: Zope/trunk/doc/CHANGES.rst
===
--- Zope/trunk/doc/CHANGES.rst 2009-05-06 16:19:56 UTC (rev 99792)
+++
Previously Lennart Regebro wrote:
On Tue, May 5, 2009 at 13:27, Wichert Akkerman wich...@wiggy.net wrote:
But you can use a lot of the Zope Toolkit with Zope 2.10, which is an
enormous benefit. If that was not possible a lot of the things people
want to do with Plone would not be possible.
Wichert Akkerman wrote:
The problem here is setuptools, not subversion. setuptools changes its
behaviour based looking at internal datastructures for a specific source
control system. You can't blame that on svn.
Sure I can. That's two major released in a row they've made the client
side
On Wed, May 6, 2009 at 09:55, Wichert Akkerman wich...@wiggy.net wrote:
No, I need to use some later versions of some packages than included in
Zope 2.10 to be able to use things like z3c.form and dexterity.
Well, mixing versions and using versions of packages that differ
several years in
i found two bugs in the current zope 2.12 beta:
1. standard_error_message is not used, this is due to code in
ZPublisher/HTTPResponse.py, method _error_html(self,title,body)
comment: XXX could this try to use standard_error_message somehow?
so could it? i'm willing to give it a try and
On 06.05.09 10:55, Jürgen Herrmann wrote:
where can i report these two bugs? ...or maybe a fix for 1.
https://bugs.launchpad.net/zope2/
Andreas
begin:vcard
fn:Andreas Jung
n:Jung;Andreas
org:ZOPYX Ltd. Co. KG
adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany
https://bugs.launchpad.net/zope2
-Tom
Jürgen Herrmann wrote:
i found two bugs in the current zope 2.12 beta:
1. standard_error_message is not used, this is due to code in
ZPublisher/HTTPResponse.py, method _error_html(self,title,body)
comment: XXX could this try to use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jürgen Herrmann wrote:
i found two bugs in the current zope 2.12 beta:
2.Script Python instances don't execute anymore. not the ones already in
the db from the zope 2.10 install i used before nor newly created ones.
traceback:
*
Hey,
Sebastien Douche wrote:
[snip]
* there's a buildbot
http://zope.buildbot.securactive.org/
http://grok.buildbot.securactive.org/
(missing repoze and zc.builout)
Thanks. Could you add a page to the zopetoolkit documentation about this
please? Otherwise again I will look through the
Hey,
Martin Aspeli wrote:
I'd be happy with that kind of policy.
Maybe you can help Sebastien Douche document the existing infrastructure
in the zopetoolkit website. It just has to be a page with a few
paragraphs so we won't keep *forgetting* that this exists and people can
find out about
Summary of messages to the zope-tests list.
Period Tue May 5 12:00:00 2009 UTC to Wed May 6 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Tue May 5 21:05:38 EDT 2009
URL:
Jürgen Herrmann wrote:
1. standard_error_message is not used, this is due to code in
ZPublisher/HTTPResponse.py, method _error_html(self,title,body)
comment: XXX could this try to use standard_error_message somehow?
The code you're referring to is as old as the hills, so I don't think
Jürgen Herrmann wrote:
2.Script Python instances don't execute anymore. not the ones already in
the db from the zope 2.10 install i used before nor newly created ones.
traceback:
Yes they do ;-)
* Module ZPublisher.Publish, line 208, in publish_module_standard
* Module
On Tuesday 05 May 2009, Chris McDonough wrote:
Were this some other project, I'd ask the Plone folks or some other group
that cares about Zope packages under 2.4 to set up a buildbot that tested
the ZTK under Python 2.4. Then I'd ask the same folks to to pay
attention to the buildbot output
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Hanno Schlichting wrote:
Personally I don't care if the ZTK doesn't officially support Python 2.4
anymore, as long as nobody will try to actively remove Python 2.4
support. For my part I'd be happy to take care of the BBB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Jürgen Herrmann wrote:
2.Script Python instances don't execute anymore. not the ones already in
the db from the zope 2.10 install i used before nor newly created ones.
traceback:
Yes they do ;-)
* Module
On 06.05.09 19:47, Tres Seaver wrote:
Chris Withers wrote:
Jürgen Herrmann wrote:
2.Script Python instances don't execute anymore. not the ones
already in
the db from the zope 2.10 install i used before nor newly
created ones.
traceback:
Yes they do ;-)
* Module
Tres Seaver wrote:
The burden of proof *is* the work you just signed up the preserve
2.4 group for: monitoring the packages they care about for things
which break under 2.4, and proposing 2.4-compatible fixes.
Sure. That's different to saying officially that ZTK does not support
Python 2.4,
27 matches
Mail list logo
