The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2286
Blamelist: dman13,jim
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zope3-
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2283
Blamelist: benji_york,jim
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zo
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Linux remy.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2282
Blamelist: jim
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zope3-dev mai
Tim Peters wrote:
I hesitate to suggest that the buildbot run with -vv too, but it sure
would have saved Jim and me time in this case.
+1
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http
We have five of these over the last 90 minutes or so:
[EMAIL PROTECTED]
> The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Linux remy.
Jim is on the case, so they'll stop in our lifetime ;-) The damnable
thing is that the log file says:
Ran 8941 tests with 0 failures and 3 e
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Linux remy.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2281
Blamelist: jim
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zope3-dev mai
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Linux remy.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2280
Blamelist: benji_york,jim
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zo
On Dec 16, 2005, at 4:56 PM, Gary Poster wrote:
...
I think I can fix it by using the pytz.reference.FixedOffset
class. That's what I'll try to do now.
BTW, let me note that this is still bad. These things *should not*
be persisted: they will generate lots and lots of little instances.
On Dec 16, 2005, at 4:20 PM, Benji York wrote:
Gary zope/i18n/format.py:141 and 149
Yup: the pytz StaticTzInfo is being used in a non-API way, and while
pickling works, unpickling doesn't (ew!).
Here's the interactive prompt example, if anyone cares.
>>> import pytz.tzinfo
>>> tz = pytz.t
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Linux remy.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2278
Blamelist: jim
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zope3-dev mai
Dieter Maurer wrote:
Jim Washington wrote at 2005-12-13 21:40 -0500:
...
Now, looking closer at the code, a ping like this might be not too bad,
because isConnected() is only called when a connection is requested, not
for every SQL statement executed. So, it might not be so onerous as
or
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Linux remy.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2277
Blamelist: tim_one
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zope3-dev
Wow, that subject line is incredibly spammy. Oh well...
I've done a pass through all the XXX marked code in the zope package and
fixed all of them but these four. Below are the person I would like to
look at/fix the XXX, the file name, and the line.
Stephan zope/viewlet/README.txt:147
Gary
We had some bugs in our code if it ran with virtual hosting, so Benji
and I talked about a fun, quick, somewhat hacky way to get virtual
hosting functional tests "for free": get your standard, already-
existing testbrowser-based functional tests to run with the virtual
hosting going on behin
[Tim Peters, on the testRunIgnoresParentSignals failure]
>
> That's definitely the problem here, and is easy to reproduce by
> inserting a short time.sleep() inside os.rmtree():
Should have said shutil.rmtree(); anyway:
> I'll try to fix it later today if I can make time, and nobody else
> d
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Linux remy.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2276
Blamelist: benji_york,jim
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zo
The Buildbot has detected a failed build of Zope3 branches Zope-3.1 2.4 Windows
2000 zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: The web-page 'force build' button was pressed by '':
Build Source Stamp: None
Blamelist:
BUILD FAILED: failed failed slave lost
sincerely,
-T
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2261
Blamelist: andreasjung,hdima,jim,jmo,mgedmin,sidnei,tim_one
BUILD FAILED: failed failed slave lost
sincerely,
-The B
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2270
Blamelist: hdima,mgedmin,shh,yuppie
BUILD FAILED: failed test
sincerely,
-The Buildbot
The Buildbot has detected a failed build of zope.testing trunk Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2258
Blamelist: andreasjung,ctheune,hdima,jim,jinty,jmo,sidnei,tim_one,tseaver,yuppie
BUILD FAILED: failed test
sincerely,
-
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Roger Ineichen wrote:
[Martijn goes into why this might be slow]
Yes you are right. Do you have another idea?
A fairly drastic one, unfortunately -- catalog all role and permission
assignments and ru
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Roger Ineichen wrote:
>
> [Martijn goes into why this might be slow]
>
>> Yes you are right. Do you have another idea?
>
>
> A fairly drastic one, unfortunately -- catalog all role and permission
> assignments and run a que
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
> Christian Theune wrote:
>
>> Hi,
>>
>> although Zope runs on platforms different than Linux, we'll have a hard
>> time to certify it on multiple platforms. Usually a very specific system
>> configuration is given, like "Windows 200
Roger Ineichen wrote:
[Martijn goes into why this might be slow]
Yes you are right. Do you have another idea?
A fairly drastic one, unfortunately -- catalog all role and permission
assignments and run a query as soon a user is removed.
Hm, perhaps another idea would involve the timestamp o
Christian Theune wrote:
Hi,
Am Freitag, den 16.12.2005, 07:49 -0500 schrieb Jim Fulton:
Christian Theune wrote:
I think if we can guarantee never to reuse a user id, provide a tool for
doing RIP and we do not provide undo we are fine.
Only if we manage the user ids. We often get principal
Hi,
Am Freitag, den 16.12.2005, 07:49 -0500 schrieb Jim Fulton:
> Christian Theune wrote:
> > I think if we can guarantee never to reuse a user id, provide a tool for
> > doing RIP and we do not provide undo we are fine.
>
> Only if we manage the user ids. We often get principal ids from outside
Christian Theune wrote:
Hi,
Am Freitag, den 16.12.2005, 07:16 -0500 schrieb Jim Fulton:
This is only a problem if username === user id. In both Zope 2 and
Zope 3, these are distinct, although this isn't widely recognized or
leveraged in Zope 2. I don't think it is necessary to remove all
gra
Jim Fulton wrote:
...
> If we
need to be able to do this, we should design support into the
authorization system that we certify.
I'll note that this implies that the grants are stored centrally.
There are a number of reasons why this might be beneficial.
It's interesting to note that on Unix
Hi,
Am Freitag, den 16.12.2005, 07:16 -0500 schrieb Jim Fulton:
> This is only a problem if username === user id. In both Zope 2 and
> Zope 3, these are distinct, although this isn't widely recognized or
> leveraged in Zope 2. I don't think it is necessary to remove all
> grants to an old user *
Christian Theune wrote:
...
I guess we have to add a generic subscriber for this and cleanup all
grant information in the object's annotation.
That leads me to the question of local event subscribers ... Do they
exist?
No. I don't see why you need them here. You don't need a local subscribe
Christian Theune wrote:
Hi,
within the certification we once created a list (drawn from the CC
catalogue) of functionality we want to support.
One of those is called "Residual Information Protection" (RIP)
The meaning of RIP is that when you delete security attributes (roles,
users, groups, pe
Hi Martijn
[...]
> [Christian]
> >> Otherwise this function is likely to become a performance
> killer, as
> >> I'd have to go all over the place to remove stuff.
> >
> > We do this everytime we delete a object. This is done with
> subscribers
> > and dispatching events to sublocations if a
Am Freitag, den 16.12.2005, 12:52 +0100 schrieb Martijn Faassen:
> Roger Ineichen wrote:
> [Christian]
> >> Otherwise this function is likely to become a performance killer, as
> >> I'd have to go all over the place to remove stuff.
> >
> > We do this everytime we delete a object. This is done w
I'm hoping to redo the internal details of a
adapter registries in the next release cycle, along the lines of
work done in the jim-adapter-redesign branch. This redesign has
the following goals:
- Bring the adapter-lookup algorithm closer to the somewhat familiar
method-lookup algorithm for P
Roger Ineichen wrote:
[Christian]
Otherwise this function is likely to become a performance killer, as
I'd have to go all over the place to remove stuff.
We do this everytime we delete a object. This is done with subscribers
and dispatching events to sublocations if a ObjectRemoveEvent get f
Jeff Shell wrote:
On 12/15/05, Martijn Faassen <[EMAIL PROTECTED]> wrote:
[snip]
One troublesome scenario I can imagine is that if I make my total
skin in Zope 3.n, it works, and then Zope 3.n + 1 is released and
it has a more specific view registered for some content object that
I'm using. I w
Hi,
Am Freitag, den 16.12.2005, 11:14 +0100 schrieb Roger Ineichen:
> > This is a simple example of what can happen when you only partially
> > delete security attributes. And it is a known problem with
> > todays Zope 2
> > security.
>
> Yes, that is excatly what we d right now. If we remova a
Hi Christian
interesting question!
This is really a missing part in Zope3.
> Hi,
>
> within the certification we once created a list (drawn from the CC
> catalogue) of functionality we want to support.
>
> One of those is called "Residual Information Protection" (RIP)
>
> The meaning of RIP is
Hi,
within the certification we once created a list (drawn from the CC
catalogue) of functionality we want to support.
One of those is called "Residual Information Protection" (RIP)
The meaning of RIP is that when you delete security attributes (roles,
users, groups, permission grants/denials) y
Benji York wrote:
Two of the three lines of _quote are comments about why the method
exists, is there something that you'd like added? Perhaps it shouldn't
be a method at all, but refactored to be inline (with comments).
Inline would be the way I'd go, as it'll stop people (mis)using the
met
On 12/15/05, Martijn Faassen <[EMAIL PROTECTED]> wrote:
> Jim Fulton wrote:
> > Martijn Faassen wrote:
> [snip]
> > > Or am I wrong in even imagining this would be desirable?
> >
> > I think so. If there are custom views for more specific interfaces,
> > it is likely those custom views provide fe
Hi,
Am Mittwoch, den 14.12.2005, 10:47 -0500 schrieb Jim Fulton:
> Yes. The customers of ours most likely to care about this
> use Windows. I would say in general, for better or worse, the decision
> makers who would care about CC would also care about Windows. I suspect that
> the decision mak
42 matches
Mail list logo
