It's been a while since the last beta, and I haven't
seen many (if any) changes checked into the 2.6 tree
in a while.
What's the holdup? With all the problems that exist with
2.6.1 (with packing, especially) I would have thought
2.6.2 would have been out months ago.
--andy.
On Thu, 31 Jul 2003 12:57am, Anthony Baxter wrote:
Anthony Baxter wrote
Updating it by hand to ZEO2 hasn't made all good and happy, though -
the ZEO/start.py includes
import ThreadedAsync.LoopCallback
at the top of the file, but the sys.path magic that makes this
available is inside the
On Thu, 31 Jul 2003 8:49am, Shane Hathaway wrote:
Andrew Sydelko wrote:
I've seen no problems with imports. And if anything, the cache
implementation in the ZODB3.1.2 version of ZEO made a remarkable
performance difference.
... as compared with earlier versions or later versions? I hope it's
On Wed, 30 Jul 2003 17:21:51 +1000 Anthony Baxter [EMAIL PROTECTED] wrote:
So I see ZEO clients here falling over all over the place under current
2.6 with:
2003-07-30T07:01:04 ERROR(200) ZEO uncaptured python exception,
closing channel ZEO.zrpc.asyncRPC connected '' at 0xc57198
.
.
On Mon, 25 Nov 2002 13:56:34 + Chris Withers [EMAIL PROTECTED] wrote:
Andrew Sydelko wrote:
Ok, whoever is in charge of zope.com releases of things
like DCOracle2, Zope and ZEO need to decide if the release
file names are going to end in .tar.gz or .tgz.
Why does it matter?
I have
On Mon, 25 Nov 2002 16:29:45 + Toby Dickenson [EMAIL PROTECTED]
wrote:
On Monday 25 November 2002 2:03 pm, Andrew Sydelko wrote:
You'll see that when I switched to ZEO 2.0 I had to change the
URL.
No doubt you had to change alot more too. This was a major release. Lots of
things
Ok, whoever is in charge of zope.com releases of things
like DCOracle2, Zope and ZEO need to decide if the release
file names are going to end in .tar.gz or .tgz. The inconsistency
between releases is quite annoying. I know that I've been
hit by it both from DCOracle2 and ZEO. The actual Zope
I've got a ZEO server that's using Zope 2.5.1 (Python 2.1.3)
and ZEO 1.0. I try initiating a pack from the Database Management
Control Panel and it starts doing it's thing. The unpacked
database is 7.5GB and after writing about 5GB to Data.fs.pack
it seems to stop packing. lsof no longer shows
On Tue, 18 Jun 2002 11:20:21 -0400 Jeremy Hylton [EMAIL PROTECTED] wrote:
AS == Andrew Sydelko [EMAIL PROTECTED] writes:
AS Trying Zope 2.6.0a1 and ZEO 2.0a1. The storage server seemed to
AS come up fine, but when trying to start the ZEO client it pretty
AS much sucked.
It looks
On Tue, 18 Jun 2002 12:19:19 -0400 Jeremy Hylton [EMAIL PROTECTED] wrote:
It wouldn't surprise me if this is a completely unrelated problem.
Any chance that the python your using to test doesn't have large file
support? Check by importing test.test_largefile.
Yeah, you're right, I don't
On Tue, 18 Jun 2002 23:01:57 -0400 Jeremy Hylton [EMAIL PROTECTED] wrote:
AS == Andrew Sydelko [EMAIL PROTECTED] writes:
AS Can someone tell me exactly how to compile python 2.1.3 with LFS
AS support?
I don't have the URL handy, but it's section 8.1.1 of the manual
IIRC. Look
On Fri, Apr 12, 2002 at 09:57:13PM +0200, Dieter Maurer wrote:
Envelope-to: [EMAIL PROTECTED]
From: Dieter Maurer [EMAIL PROTECTED]
To: Andrew Sydelko [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [Zope-dev] problems downloading CVS tarballs
X-Spam-Status: No, hits=-13.5 required=5.0
When I try to download a CVS tarball of the Zope_2_5-branch branch, I get
a corrupt tar archive. The .../ISO_8859_1_Splitter/src directory
contains one
c file whose name gets truncated. I'm using gnutar so I'm pretty sure
it's not
a problem on my end.
What tar is used on the CVS server?
I'm curious as to what is holding up Zope 2.5.1? 2.5.1b1 has been out for
quite a while now (in Zope time).
--andy.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
For some reason, when I try to view the Version Management screen
under Control Panel, I get a bunch of gibberish for one of the versions...
And... it won't let me click on the check box and Discard it... Is there
a way to do this manually? Or even see which versions are available manually?
We
On Monday 04 March 2002 11:08, you wrote:
On Mon, 4 Mar 2002 11:01:22 -0500
A low-level way to get a list of versions is to call the
versions() method on the storage object. Example:
from ZEO.ClientStorage import ClientStorage
cs = ClientStorage(...) # your server address here
Trying to start a ZEO client using Zope 2.5.0b4 doesn't
work:
--
2002-01-15T20:13:20 INFO(0) client Trying to connect to server: ('192.168.1.52', 8900)
--
2002-01-15T20:13:20 INFO(0) ClientStorage Connected to storage
--
2002-01-15T20:13:20 ERROR(200) ZODB Couldn't load state for
Jeremy Hylton wrote:
Could you just undo enough transactions to get back to the old state?
Or do you need to keep some of the changes you made?
I'm not familiar with any tools that can go through
transactions like this. Can you poing me towards
a tool that allows me to see all the transactions
Chris McDonough wrote:
Try the original tranalyzer here instead:
http://www.zope.org/Members/tsarna/Tranalyzer
That's better, but it bombs out part way thru:
Traceback (most recent call last):
File ./tranalyzer.py, line 333, in ?
main(sys.argv)
File ./tranalyzer.py, line 325, in main
Chris McDonough wrote:
Note that untarring the attached products into your 2.4 Products
directory should allow you to start 2.4 up with the Data.fs from your
foray into 2.5 without needing to truncate anything. At that point you
should be able to delete the session_data_manager,
Chris McDonough wrote:
Make sure you try the unscrew.py thing I sent over before doing that...
Just tried it. It seemed to run fine, but I still get 404 Not found on
/manage_main and 400 Bad Request on /
--andy.
___
Zope-Dev maillist - [EMAIL
Chris McDonough wrote:
Make sure you try the unscrew.py thing I sent over before doing that...
sitting here waiting for you response to my last email saying that
didn't work, I realized I hadn't deleted the cache before restarting.
So, now that that the cache is gone, I restarted it up and it
So, I thought I fixed my problems... But now I can't get
to / or /manage_main again. Although I _can_ ftp in to
see stuff.
I don't understand the problem here...
/ returns 400 Bad Request
/manage_main returns 404 Not Found
--andy.
___
Zope-Dev
Brian Lloyd wrote:
Clicking on Cache detail in the Debug Information
Control Panel, I get the following traceback:
Zope Error!
Zope has encountered an error while publishing this resource.
Error Type: AttributeError
Error Value: __module__
Hi Andrew -
I'm not able to
Our Zope installation has this really strange
problem associated with the displayed
Modification Time shown for each file in
the /manage_main of a folder. The time that
is shown is exactly one-hour later than
the system time. I think I've tracked down
this to the bobobase_modification_time
25 matches
Mail list logo
