On 24 Feb 2014, at 11:16 , Vincent Pelletier vinc...@nexedi.com wrote:
On Sat, 22 Feb 2014 10:37:38 -0500,
Jim Fulton j...@zope.com wrote :
I've created a new ZODB mailing list via google groups:
https://groups.google.com/forum/#!forum/zodb
If others are wondering how to join the group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/24/10 00:11 , Laurence Rowe wrote:
I created the zodbdocs following the examples of zope2docs and
zope3docs for docs.zope.org. Jens Vagelpohl added them to the cron job
that updates docs.zope.org and is the person responsible for that site
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
... just to check if the list is broken as Martin Aspeli seems to believe.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkxaZjQACgkQRAx5nvEhZLJnOwCfRosCbl5sQH8cuD1ZwNG2r7NN
aFQAn1MVXOXYErTz9Rmd0dkJyXAkSl6U
=ED9Q
-END
Hi all,
In a system using Zope 2.11 and ZODB 3.7.0b3 I'm having a problem with
old transaction records containing pickle data that fails on
cPickle.Unpickler.noload as employed by ZODB.serialize.referencesf, I
get an AttributeError from inside the cPickle module:
def referencesf(p, oids=None):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/14/10 10:19 , Shane Hathaway wrote:
On 06/14/2010 01:43 AM, Jens Vagelpohl wrote:
My question: Is there any risk associated with ignoring the failure
during packing? The latest object versions for the persistent objects in
question do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/12/10 13:21 , Jim Fulton wrote:
On Wed, May 12, 2010 at 7:16 AM, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/12/10 13:07 , Jim Fulton wrote:
B. Change ZODB so that the root object is a variant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/27/10 12:29 , Hanno Schlichting wrote:
On Mon, Apr 26, 2010 at 7:44 PM, Jim Fulton j...@zope.com wrote:
What do folks think about this? Should missing records be ignored? Or
should the missing record cause the pack (or maybe just GC) to fail?
On Sep 14, 2009, at 13:10 , Chris Withers wrote:
Jim Fulton wrote:
ZODB doesn't provide any direct support because it has no notion of
tree.
Does it have any notion of object size on disk for a given object?
In Zope 2, you could export the folder and look at the size of the
export.
On Sep 14, 2009, at 13:27 , Chris Withers wrote:
Jens Vagelpohl wrote:
Sadly, when you're trying to figure out which folder is using all
the
space on a disk that's running out of space, that's not practical...
How about simply writing a script that crawls the ZODB and gives
you paths
On Jul 31, 2008, at 17:23 , Chris Withers wrote:
I didn't realise (and I've done it often and never experienced this
in the past) than running a zopectl run script from the same
instance home as a running client could result in ZEO client cache
corruption.
Should this be the case?
On Jul 31, 2008, at 17:37 , Chris Withers wrote:
Jens Vagelpohl wrote:
Sounds logical to me. The running instance and your zopectl run-
script work in the same space with identical configurations, so
both will start using the same ZEO cache file. To me this sounds
like a recipe
On Feb 5, 2008, at 01:57 , Chris Withers wrote:
Hi All,
Where can I find the zodb tools (fsrefs.py, fstest.py, etc) as
appropriate for the zodb that ships with Zope 2.9.6?
iirc, 2.9.6 was one of the releases that didn't ship with ZODBTools
due to a bug, so I'm looking for places to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3 Aug 2007, at 06:56, David Pratt wrote:
I ask this since setting threads to 1 improved performance
according to the recent high performance zope session by Lovely
systems at europython.
Just setting the number of threads to 1 won't improve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10 Apr 2007, at 20:19, Alan Runyan wrote:
File /usr/local/python-2.4.4/lib/python2.4/asyncore.py, line
343, in rec
v
data = self.socket.recv(buffer_size)
error: (113, 'No route to host')
File
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21 Mar 2007, at 17:29, Chris Withers wrote:
I'm hoping for some means to just lop transactions off the end of
the Data.fs until I get to the point in time I want...
Why don't you just record the exact size of your Data.fs before
starting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28 Jan 2007, at 00:18, Simon Burton wrote:
I have a Persistent object, however, its attributes only
get loaded from the storage when I request a specific attribute.
Problem is, I don't know the names of the attributes
necessarily. I was trying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2 Oct 2006, at 14:07, Russ Ferriday wrote:
But for an app to be writing into thin air without complaining -
THAT's a bug!
Even having a backup of the Data.fs would not help!
Not picking on zope, but if that's what's happening it has to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7 Jun 2006, at 11:53, Richard Jennings wrote:
Hi,
I have a Zope2.7.2/Zeo2.2.2 instance running, using the standard
zope.conf
zeo.conf settings (exception: port=8081) and it works fine. I want
read-only
access to the instance zodb to read
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29 May 2006, at 16:45, Christian Theune wrote:
[EMAIL PROTECTED] wrote:
Hi folks, I'm looking at making a scalable zope infrastructure, I
can scale the ZEO clients and mysql, the only issue is the ZEO
server. I have used drbd and heartbeat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29 May 2006, at 16:59, [EMAIL PROTECTED] wrote:
If you setup drbd and heartbeat , the spare will take over the
floating ip from the zeo server and restart the service. drbd is
simply doing a block level replication of the zeo server file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26 May 2006, at 05:46, David Pratt wrote:
I am curious how folks are handling authentication for ZEO in a
general way (client against the server). Is is common to attempt to
use user/passwords from acl in zope as a means of creating a lists
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5 May 2006, at 02:57, David Pratt wrote:
Hi Jim and Roderigo! This is encouraging news. I have been putting
much thought into this also. There is a downside to refactoring ZEO
in that there are many folks heavily dependent on it and also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25 Apr 2006, at 09:01, Thomas Guettler wrote:
I think it is a bug.
If you think there is a bug please use the collector:
http://www.zope.org/Collectors/Zope
Email gets lost and forgotten, it is unsuitable for reporting bugs.
jens
On 25 Jan 2006, at 09:49, Rene Pijlman wrote:
Option 3:
Use separate Python installations for Zope and the application.
Install ZODB in the application's Python installation, not in
Zope's.
This is the only sane option.
jens
___
For more
On 9 Jan 2006, at 21:21, Ammar Hakim wrote:
Sometimes, in the last step the browser still gets the
old data before the change was made. On a refresh,
however, the correct data is obtained. Further, this
problem does not always crop up: it seems that it
occurs if the particual DB operation is
On 11 Dec 2005, at 16:35, Jim Fulton wrote:
Tim Peters wrote:
[Jens Vagelpohl]
Just as a heads-up because I don't know how much testing ever
gets done
on OS X:
I do: none ;-)
Can someone volunteer to run a Mac OS X buildbot slave? If not,
I'll try to set up an *old* iMac that the PSF
Just as a heads-up because I don't know how much testing ever gets
done on OS X: Running the tests on the current ZODB trunk using a
self.built Python 2.4.2 on OS X (10.4.3) the following test fails:
Failure in test test_must_use_consistent_connections
On 12 Jul 2005, at 18:17, Lennart Regebro wrote:
previous Zope version, which I used, was 2.6.1, but it was very old
version and
I decided to jump to 2.8.0. I took problems with autorefresh. What
can I do to solve
my problems?
If it creates problems then simply don't use it.
That's not a
Imagine if somebody tried to use ZPTs, and the answer to any question
where you get errors from it is well, then don't use it? It's just
not a viable answer.
Refresh is not a core functionality like ZPT. That comparison is a
bit outlandish.
If it is the majoritys agreement that this
On 2 Jul 2005, at 01:37, Sidnei da Silva wrote:
On Mon, Jun 27, 2005 at 02:38:48PM -0400, Tim Peters wrote:
| Any suggestions about how to best implement this,
|
| Maybe just create your own socket, attempt to connect, and if
that attempt
| fails produce the kind of error message you want
30 matches
Mail list logo
