If I set my beforestorage to a reasonably current time, e.g. now, I
expect to get reasonably good performance from a ZEO client cache.
Instead, I find that beforestorage:
1) asks the cache to ``loadBefore``;
2) but that method only looks for noncurrent entries;
3) meanwhile, my cache only
On 24 October 2011 22:54, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Zope security response team, I would like to announce
the availability of a hotfix for a vulnerability inadvertently
published earlier today.
Laurence Rowe wrote:
This hotfix addresses a serious vulnerability in the Zope2
application server. Affected versions of Zope2 include:
- - 2.12.x= 2.12.20
- - 2.13.x= 2.13.6
Older releases (2.11.x, 2.10.x, etc.) are not vulnerable.
Can you confirm whether or not Zope 2.13.6 through
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/2011 07:44 AM, yuppie wrote:
Laurence Rowe wrote:
This hotfix addresses a serious vulnerability in the Zope2
application server. Affected versions of Zope2 include:
- - 2.12.x= 2.12.20
- - 2.13.x= 2.13.6
Older releases (2.11.x,
I take issue with not working properly. Before storage works
correctly with ZEO.
On Tue, Oct 25, 2011 at 5:43 AM, Malthe Borch mbo...@gmail.com wrote:
If I set my beforestorage to a reasonably current time, e.g. now, I
expect to get reasonably good performance from a ZEO client cache.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/2011 07:28 AM, Laurence Rowe wrote:
On 24 October 2011 22:54, Tres Seaver tsea...@palladion.com
wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On behalf of the Zope security response team, I would like to
announce the
This is the summary for test reports received on the
zope-tests list between 2011-10-24 00:00:00 UTC and 2011-10-25 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Woohoo -- down to just seven!
[1]FAILED ZTK 1.1 / Python2.5.5 Linux 64bit
https://mail.zope.org/pipermail/zope-tests/2011-October/051688.html
This
has the sub-process buffer failure for which I checked in a fix
today from Jonathan Ballet: