I would like to consider the 2.7 branch closed for any kind of fixes except
security related fixes. I don't plan any further 2.7 releases.
-aj
--On 15. Dezember 2005 21:53:38 -0500 Chris McDonough <[EMAIL PROTECTED]>
wrote:
Looks good!
On Dec 15, 2005, at 4:47 PM, Sidnei da Silva wrote:
Looks good!
On Dec 15, 2005, at 4:47 PM, Sidnei da Silva wrote:
I would like to merge this patch to all the branches back to Zope 2.7,
anyone would care to review or is against it?
http://www.zope.org/Collectors/Zope/1976
--
Sidnei da Silva
Enfold Systems, LLC.
http://enfoldsystems.com
__
On 12/16/05, Dennis Allison <[EMAIL PROTECTED]> wrote:
> MAYBE CONFLICTS AND THEIR RESOLUTION ARE NOT THE ROOT CAUSE OF THE SESSION
> VARIABLE PROBLEM. The observed problem is that session variables suddenly
> disappear.
Perhaps your app is tripping over some bug in conflict handling. But
I'd say
I would like to merge this patch to all the branches back to Zope 2.7,
anyone would care to review or is against it?
http://www.zope.org/Collectors/Zope/1976
--
Sidnei da Silva
Enfold Systems, LLC.
http://enfoldsystems.com
___
Zope-Dev maillist - Zop
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2241
Blamelist: ctheune,jim,tim_one,tseaver,yuppie
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
On Thu, 15 Dec 2005, Chris McDonough wrote:
> Trimmed zodb-dev off the cc list.
>
> On Dec 15, 2005, at 2:24 PM, Dennis Allison wrote:
>
> > The systems are running a Zope/ZEO combination with a store
> > configuration
> > of:
> >
> > #
> >
> > # Temporary storage database (for sessions
Trimmed zodb-dev off the cc list.
On Dec 15, 2005, at 2:24 PM, Dennis Allison wrote:
The systems are running a Zope/ZEO combination with a store
configuration
of:
#
# Temporary storage database (for sessions)
name temporary storage for sessioning
mount-point /t
Zope 2.8.4, ZODB 3.4.2
Chris,
I'm pretty sure that I mentioned having done that in one of my postings.
I have followed your recommendations, but the problem remains. (um...
persists )
The systems are running a Zope/ZEO combination with a store configuration
of:
#
# Temporary storage d
[Chris McDonough]
> Note that changing the transientobject conflict resolution algorithm
> won't get rid of all write conflict errors, because the BTree-based
> indexes in the transient object container will still conflict during a
> "bucket split" and other situations that I can't exactly recall
>
Code would be good.
Note that changing the transientobject conflict resolution algorithm
won't get rid of all write conflict errors, because the BTree-based
indexes in the transient object container will still conflict during
a "bucket split" and other situations that I can't exactly recall
--On 15. Dezember 2005 17:55:16 +0100 Martijn Faassen <[EMAIL PROTECTED]>
wrote:
Hm, so it auto-decodes non-unicode strings using UTF-8? That's a bit
dangerous, as you suppress a large class of unicode errors in the code.
Code that creates UTF-8 strings will be silently accepted. Not as bad as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey all,
I'm currently trying to setup a custom zope instance for our c.s.
department at school. Currently we run a totally linux infrastructure
with ldap authentication which we would also like to tie into zope. My
question is not how to authenticate
Andreas Jung wrote:
--On 9. Dezember 2005 10:11:42 -0500 Jim Fulton <[EMAIL PROTECTED]> wrote:
We need to migrate Zope 2 to use a similar strategy. We need volunteers
to brainstorm how this can be done and make one or more proposals.
This is likely a prerequisite for finishing the publisher
Florent Guillaume wrote:
Martijn Faassen wrote:
[snip]
What I'm worried about doing this for old code, but some steps will
probably become clear during the brainstorming session. Migration
tools that turn strings in the ZODB into unicode ones magically (with
the ability to spell out exception
Summary of messages to the zope-tests list.
Period Wed Dec 14 12:01:01 2005 UTC to Thu Dec 15 12:01:01 2005 UTC.
There were 8 messages: 8 from Zope Unit Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-2_7-branch Python-2.4.2 :
Linux
From: Zope Unit Tests
Date: Wed
[Using zope-dev@ instead of [EMAIL PROTECTED]
Dennis Allison wrote:
A more session-friendly conflict resolution might use:
1. if any of the states are invalid (that is, has a key '_invalid')
return the invalid state.
2. if any any of the states attributes ['token','id','_created
Yup, that box is slowly dying on me. I will take down the nightlies
until I find a new machine to run them on.
Stefan
On 14. Dez 2005, at 15:35, Chris McDonough wrote:
FYI: These tests appear to be failing due to a race in the tests
they're exercising that could be exposed if the machine
Hello.
At Fri, 09 Dec 2005 10:11:42 -0500,
Jim Fulton wrote:
> - Common approach to Unicode
>
> In particular, In Zope 3, all text is stored and managed as Unicode.
> The publisher decodes request data and encodes response data. The vast
> majority of application and library code can ignore enco
18 matches
Mail list logo