[Zope-dev] Re: Attention: cvs to subversion transition DONE (I hope :)
There is a problem with the public subversion access. The 'svn' urls are currently disabled. 'svn+ssh' urls are still working as is web access. I expect to have this problem resolved today. Jim Jim Fulton wrote: The conversion is done. All trunk development should be done in the subversion repository for Zope (Zope 2), Zope3, ZODB, ZConfig, and zdaemon. (zLOG is not broken out as a separate project because it's now only used by Zope.) For information on using the Zope subversion repository, see: http://dev.zope.org/Subversion and especially: http://dev.zope.org/Subversion/ZopeSVNFAQ I'm gonna wait a few days before removing files from the CVS head, just to be safe. :) I will check in some marker files, warning people to work in svn. Finally, before the conversion, I tagged the cvs head with the cvs-to-svn-conversion tag. If you have outstanding head work, you should be able to update to that tag and then use cvs diff to generate patch files to be applied to subversion checkouts. Jim Jim Fulton wrote: I'm about to begin the conversion now. Please don't make any more changes to the Zope, Zope3, ZODB, ZConfig, zLOG, or zdaemon CVS heads. Jim Jim Fulton wrote: I plan to do the transition tomorrow, Tuesday may 11. I'll begin at 10am US/Eastern and be done by 5pm US/Eastern. During this time, I ask that no one make checkins to the CVS head for those projects. The first thing I will do is to tag the head with the tag: 'cvs-to-svn-conversion'. When I'm done, I will remove all files from the heads of the preojects in CVS, except README.txt files giving subversion access instructions. Jim Jim Fulton wrote: Jim Fulton wrote: Sorry for the false start. I totally missed a flaw in subversion's handling of text-file line endings. I suspect that this is fixable, but it's not going to be fixed today. I think that this issue has been resolved. I have updated my cvs to svn conversion software to set the svn:eol-style property to native on text files so that they will get Windows line endings when checked out on Windows and Unix line endings when checked out on Unix-based systems. I've updated the demonstration repository with the results of this conversion. Note that it's possible that existing checkouts will need to be discarded, as I've totallly rebuilt the repository. To browse the respository: http://svn.zope.org/ To do a read-only checkout: svn co svn://svn.zope.org/repos/main/project/trunk or, to do a writable checkout: svn co svn+ssh://svn.zope.org/repos/main/project/trunk Developers who add new files will need to set the svn:eol-style property on new text files. There are ways to automate this and we'll provide some guidence on this at: http://dev.zope.org/Subversion BTW, someone has done some work on that Wiki, which was a copy of dev.zope.orf/CVS, to convert the CVS references and instructions to refer to and document Subversion instead. Thanks! I think that there is still a good bit of work to do. Volunteer help would be much appreciated. I'm thinking of trying again to do the cvs to svn conversion of the main-line development branches (cvs heads) on Tusday May 11. This would entail moving ZODB, Zope 2, and Zope 3 head development to subversion (along with ZConfig, zdaemon, and zLOG). Any objections? Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: How To run current Zope 2 3 from CVS on Windows
Hi, When Zope 2/3 runs in Cygwin, does it run in daemon mode? What does import os; print os.name return in Cygwin, nt or posix? I run ZEO's start.py (from Zope 2.6.2, compiled in Windows by MSVC) in MSYS, os. name is nt, so it does not run in daemon mode. Thanks! Regards, ZhiMin On Mon, 3 May 2004 10:25:50 -0400, Tim Peters [EMAIL PROTECTED] wrote: [Max M] As I said, I would write a How-To in getting Zope 3 up and running on Windows, given the binaries that Tim has made. http://www.mxm.dk/papers/run-z3-cvs-wthout-compiler/ Feel free to comment. Nicely done! Thank you for doing this. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [Zope3-dev] Re: How To run current Zope 2 3 from CVS on Windows
At 06:12 PM 5/12/04 +0800, Choo Zhi Min wrote: What does import os; print os.name return in Cygwin, nt or posix? Python 2.3.2 (#1, Oct 9 2003, 12:03:29) [GCC 3.3.1 (cygming special)] on cygwin Type help, copyright, credits or license for more information. import os os.name 'posix' ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Attention: cvs to subversion transition DONE (I hope :)
Jim Fulton wrote: There is a problem with the public subversion access. The 'svn' urls are currently disabled. 'svn+ssh' urls are still working as is web access. I expect to have this problem resolved today. This has been resolved. 'svn' urls are enabled again. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [ZODB-Dev] Re: BTrees strangeness (was [Zope-dev] Zope 2.X BIG Session problems - blocker - our site dies - need help of experience Zope developer, please)
On 11/05/2004, at 4:54 PM, Chris McDonough wrote: On Mon, 2004-04-26 at 18:34, Michael Dunstan wrote: I removed all the above hacks leaving just the one that comments out the construction of the to_notify list. Reran the test rig. And have yet to see any KeyErrors. Have you seen any since the time you reported this? (I chatted about this with Chris on #zope.) Since the last report I have not run been running the test rig. I Needed my laptop back so I could get on with a few other things. :-( So I'm going to see if I can show others how to recreate the test rig that I'm using here. A trivial site and the script for testing that site are attached. (Reminder - I'm using Zope 2.7.0 here - HEAD just is not ready for such games. :-) SessionRigExtensions.py and sessionrig.zexp make up the site. sessionrig.zexp is simply a bunch of external methods (with a folder to provide some separation of a standard_error_message that makes use of sessions). SessionRigExtensions.py has all the code for the external methods. TestSessionRig.py is the script which attacks zope. It should just work as is. (Unless the site you just imported is not found at http://localhost:8080/sessionrig. If that's the case then simply edit the 'path' in the code.) Don't expect the output of this script to say anything conclusive. Instead you should be tailing + greping through the event log for things of interest. Now the knobs that you should tweak to so that you see things of interest within minutes/hours rather than days/weeks... (The actual values may depend on the hardware that your running this on.) * etc/zope.conf: session-timeout-minutes 1 maximum-number-of-session-objects 1000 * lib/python/Products/Tranience: PERIOD = 1 #20 # attempt housekeeping every PERIOD seconds SPARE_BUCKETS = 2 #15 # number of buckets to keep spare * lib/python/tempstorage/TempoaryStorage.py: # keep old object revisions for CONFLICT_CACHE_MAXAGE seconds CONFLICT_CACHE_MAXAGE = 1 #60 # garbage collect conflict cache every CONFLICT_CACHE_GCEVERY seconds CONFLICT_CACHE_GCEVERY = 1 #60 * lib/python/Products/SiteErrorLog/SiteErrorLog.py: _rate_restrict_burst = 10 #5 (I wanted to see repeated errors in the event log. There is probably a more obvious way to do that. But that's what I'm using at the moment. Took me a while to actually find out this was why I was not seeing all the exceptions in the event log. Perhaps things like these should be exposed via zconfig? Makes a useful medium to document such knobs to promote awareness. As well as allowing people that are pushing zope into new corners to have a simpler way to manage these kinds of settings.) * TestSessionRig.py - there are few things that you can tweak within here too. (Well the whole script is up for grabs - hack away - I did.) As the script is it should expose problems with lack of transaction isolation for standard_error_message. I do tend to run several instances of this script at once. And in my case (as the url suggests) I run this on the same host as zope is running on. However to expose the KeyError thrown from TempoaryStorage I found that I did not really need much 'sleepiness' and replaced all the start()'s at the end of the script with start(200,1,100,10). (I suspect that you don't even need to support cookies in the client for this error. Sufficient to hit any URL that simply creates a session object on the server. And hit that URL very hard.) Another effective knob that you may try playing with is the nap duration used to slow down a session write: slowWrite = path + '/write?nap:float=0.5' hmm... that's probably enough to help someone recreate a KeyError or two. Michael. sessionrig.zexp Description: Binary data SessionRigExtensions.py Description: Binary data TestSessionRig.py Description: Binary data ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
