lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Prescott Nasser <geobmx...@hotmail.com>
Subject RE: [Lucene.Net] FW: trouble getting cms content to work correctly
Date Fri, 02 Mar 2012 03:53:21 GMT

I'm told it should "only take" about 10 minutes to publish now (as opposed to ~2.5 hours before).
No harm in trying ;) ~P
 > Date: Thu, 1 Mar 2012 21:47:49 -0500
> From: mherndon@wickedsoftware.net
> To: lucene-net-dev@lucene.apache.org
> Subject: Re: [Lucene.Net] FW: trouble getting cms content to work correctly
> 
> Is it safe to add content to the site through the CMS again?  Anything to
> be wary of or not explicitly do?
> 
> On Wed, Feb 15, 2012 at 6:30 PM, Prescott Nasser <geobmx540@hotmail.com>wrote:
> 
> >
> > Took all day, but Joe was there babysitting and correcting things for us.
> > Basically there is a bug in svn 1.6.17 that the CMS is based on, which is
> > making our commits a pain at the moment. Once that gets upgraded it should
> > be relatively smooth sailing. It won't help us though if we want still
> > planning on updating massive amounts of documentation on a regular basis.
> > Thanks Joe, I can't thank you enough for the help today.
> >  ~PrescottDate: Wed, 15 Feb 2012 14:49:48 -0800
> > From: joe_schaefer@yahoo.com
> > Subject: Re: trouble getting cms content to work correctly
> > To: geobmx540@hotmail.com
> >
> > After some testing it appears that this performancebug is fixed in svn
> > 1.7, but the CMS is currentlyrunning 1.6.17.  I hope to have the host
> > upgradedwithin the next 30 days or so, but for now I stillrecommend using
> > the script.
> >
> >        From: Prescott Nasser <geobmx540@hotmail.com>
> >  To: joe_schaefer@yahoo.com
> >  Sent: Wednesday, February 15, 2012 5:28 PM
> >  Subject: RE: trouble getting cms content to work correctly
> >
> >
> >
> >
> >
> >
> > Alright - sounds good
> >
> > Thanks again!
> >
> > ~P
> >
> > Date: Wed, 15 Feb 2012 14:25:45 -0800
> > From: joe_schaefer@yahoo.com
> > Subject: Re: trouble getting cms content to work correctly
> > To: geobmx540@hotmail.com
> >
> > I'm having some svn people look at the merge issues.Right now all I can
> > suggest is that you publish usingthe publish.pl script on
> > people.apache.org.  It's takingme about 10 min total to carry that out,
> > which is certainlytoo long given the nature of the changes it's merging,but
> > I'll let you know what I find
> >  out.
> >
> >        From: Prescott Nasser <geobmx540@hotmail.com>
> >  To: joe_schaefer@yahoo.com
> >  Sent: Wednesday, February 15, 2012 5:13 PM
> >  Subject: RE: trouble getting cms content to work correctly
> >
> >
> >
> >
> >
> >
> > It's butt ugly - all in one directory, 8206 files. I'd prefer a more
> > natural docs structure, but that's how it gets generated
> >
> > ~P
> >
> > Date: Wed, 15 Feb 2012 14:10:47 -0800
> > From: joe_schaefer@yahoo.com
> > Subject: Re: trouble getting cms content to work correctly
> > To: geobmx540@hotmail.com
> >
> > Ok lemee kill it and use the publish.pl scripton people to see if I can
> > get it to work right.Just curious tho- about how many files do youhave
> > within that docs dir- all in one dir I presume?
> >        From: Prescott Nasser <geobmx540@hotmail.com>
> >  To: joe_schaefer@yahoo.com
> >  Sent: Wednesday, February 15, 2012
> >  5:08 PM
> >  Subject: RE: trouble getting cms content to work correctly
> >
> >
> >
> >
> >
> >
> > I'm thinking still merge funk
> >
> > Date: Wed, 15 Feb 2012 14:05:21 -0800
> > From: joe_schaefer@yahoo.com
> > Subject: Re: trouble getting cms content to work correctly
> > To: geobmx540@hotmail.com
> >
> > Looks like it just completed.  Hmm, goahead and publish and lets try this
> > onemore time.
> >
> >        From: Joe Schaefer
> >  <joe_schaefer@yahoo.com>
> >  To: Prescott Nasser <geobmx540@hotmail.com>
> >  Sent: Wednesday, February 15, 2012 5:02 PM
> >  Subject: Re: trouble getting cms content to work correctly
> >
> >
> > Yeah more merge funk. Leave it run for now,but don't take any further
> > action until youhear from me.
> >
> >        From: Prescott Nasser <geobmx540@hotmail.com>
> >  To: joe_schaefer@yahoo.com
> >  Sent: Wednesday, February
> >  15, 2012 4:59 PM
> >  Subject: RE: trouble getting cms content to work correctly
> >
> >
> >
> >
> >
> >
> > I hate to be the bearer of bad news... still taking days to publish (I'm
> > not sure if there is a merge error or not) let me know I'll kill this quick
> >
> > Date: Wed, 15 Feb 2012 13:54:52 -0800
> > From: joe_schaefer@yahoo.com
> > Subject: Re: trouble getting cms content to work correctly
> > To: geobmx540@hotmail.com
> >
> > Yeah try out the webgui and edit/commit/publisha minor change.  It should
> > take you no more thana minute or so total.
> >
> >        From: Prescott Nasser <geobmx540@hotmail.com>
> >  To: joe_schaefer@yahoo.com
> >  Sent: Wednesday, February 15, 2012 4:52 PM
> >  Subject: RE: trouble getting cms content to work correctly
> >
> >
> >
> >
> >
> >
> > Man that sounds like a tool full of awesome!
> >
> > Ok - so for the moment no new docs, a simple edit should be quick?
> > Date: Wed, 15 Feb 2012 13:48:40 -0800
> > From: joe_schaefer@yahoo.com
> > Subject: Re: trouble getting cms content to work correctly
> > To: geobmx540@hotmail.com
> >
> > Ok it's now fixed and your site should work as expectedat this point.  I
> > had to redact the lazy_publish featureand reserve it for admins only
> > because you don't actuallyhave permission to completely remove your
> > publication
> >  sitefrom svn and
> >  that's not something I can offer
> >  without
> >  providingyou and every other
> >  committer with the ability to nukeeach other's entire sites.
> >
> >
> >     From: Joe Schaefer <joe_schaefer@yahoo.com>
> >  To: Prescott Nasser <geobmx540@hotmail.com>
> >  Sent: Wednesday, February 15, 2012 4:20 PM
> >  Subject: Re: trouble getting cms content to work correctly
> >
> >
> > Yeah well it's probably timing out somewhere along the line.I'm looking
> > into your svn tree now to see if I can figure outwhat's going on.
> >  Basically the svn merge it's running isdoing evil things.
> >
> >        From: Prescott Nasser <geobmx540@hotmail.com>
> >  To:
> >  joe_schaefer@yahoo.com
> >
> >  Sent: Wednesday, February 15, 2012 4:18 PM
> >  Subject: RE: trouble getting cms content to work correctly
> >
> >
> >
> >
> >
> >
> > Sorry, I'm not seeing merge errors, just seeing my browser waiting for a
> > response..I'll hold up
> >
> > Date: Wed, 15 Feb 2012 13:15:32 -0800
> > From: joe_schaefer@yahoo.com
> > Subject: Re: trouble getting cms content to work correctly
> > To: geobmx540@hotmail.com; site-dev@apache.org
> >
> > Stop Prescott when you get a merge error please.There's something funky
> > going on here that I needto dig into and running publish again won't
> > magicallyfix it.
> >
> >
> >      From: Prescott Nasser <geobmx540@hotmail.com>
> >  To: joe_schaefer@yahoo.com; site-dev@apache.org
> >  Sent: Wednesday, February 15, 2012 3:52 PM
> >  Subject: RE: trouble getting cms content to work correctly
> >
> >
> >
> >
> >
> >
> > Ah ok, I thought we were past that part - I'm losing track, just blinding
> > taking orders at this point :)
> >
> > ~P
> > Date: Wed, 15 Feb 2012 12:50:41 -0800
> > From: joe_schaefer@yahoo.com
> > Subject: Re: trouble getting cms content to work correctly
> > To: geobmx540@hotmail.com; site-dev@apache.org
> >
> > Yes as I explained before by using lazy_publishyou will incur a
> > performance hit the first timeyou subsequently publish normally.  Once
> > thiscompletes
> >  things should behave
> >  properly.
> >
> >        From: Prescott Nasser <geobmx540@hotmail.com>
> >  To: joe_schaefer@yahoo.com; site-dev@apache.org
> >
> >  Sent: Wednesday, February 15, 2012 3:48 PM
> >  Subject: RE: trouble getting cms content to work correctly
> >
> >
> >
> >
> >
> >
> > small change still seems to be taking longer than it should..
> >
> > Date: Wed, 15 Feb 2012 12:41:20 -0800
> > From: joe_schaefer@yahoo.com
> > Subject: Re: trouble getting cms content to work correctly
> > To: geobmx540@hotmail.com; site-dev@apache.org
> >
> > No a regular publish this time please.
> >
> >
> >  From: Prescott
> >  Nasser
> >  <geobmx540@hotmail.com>
> >  To: joe_schaefer@yahoo.com; site-dev@apache.org
> >  Sent: Wednesday, February 15, 2012 3:39 PM
> >  Subject: RE: trouble getting cms content to work correctly
> >
> >
> >
> >
> >
> >
> >
> > I started the regular publish - but stopped that, should I do a lazy
> > publish?
> >
> > Date: Wed, 15 Feb 2012 12:36:57 -0800
> > From: joe_schaefer@yahoo.com
> > Subject: Re: trouble getting cms content to work correctly
> > To: joe_schaefer@yahoo.com; geobmx540@hotmail.com; site-dev@apache.org
> >
> > Ok that seems to have gone thru cleanly this time.Now please make another
> > minor edit to the site andlet's flush things thru one last
> >  time.
> >
> >
> >     From: Joe Schaefer <joe_schaefer@yahoo.com>
> >  To: Prescott Nasser <geobmx540@hotmail.com>; "site-dev@apache.org" <
> > site-dev@apache.org>
> >  Sent: Wednesday, February 15, 2012 3:30 PM
> >  Subject: Re: trouble getting cms content to work correctly
> >
> >
> > I had a bug in lazy_publish- please use that insteadwhen you get an error
> > message indicating the mergefailed (like you just did).  I'll keep an eye
> > on thingswhile you do.
> >
> >        From: Prescott Nasser
> >  <geobmx540@hotmail.com>
> >  To:
> >  joe_schaefer@yahoo.com; site-dev@apache.org
> >  Sent: Wednesday, February 15, 2012 2:49 PM
> >  Subject: RE: trouble getting cms content to work correctly
> >
> >
> >
> >
> >
> >
> > So, that worked, site was all there - looking good.
> >
> > I made a small change to the index.html page (to up the words that it
> > shows from the blog roll). And hit publish - I seem to be stuck (taking
> > forever)... Not sure why that would occur?
> >
> >
> >
> > Date: Wed, 15 Feb 2012 11:31:02 -0800
> > From: joe_schaefer@yahoo.com
> > Subject: Re: trouble getting cms content to work correctly
> > To: geobmx540@hotmail.com
> >
> > Seems to have
> >  worked,
> >  no?
> >
> >     From: Prescott Nasser <geobmx540@hotmail.com>
> >  To: joe_schaefer@yahoo.com
> >  Sent: Wednesday, February 15, 2012 2:11 PM
> >  Subject: RE: trouble getting cms content to work correctly
> >
> >
> >
> >
> >
> >
> > Here's goes..
> >
> > Date: Wed, 15 Feb 2012 10:56:11 -0800
> > From: joe_schaefer@yahoo.com
> > Subject: Re: trouble getting cms content to work correctly
> > To: geobmx540@hotmail.com; site-dev@apache.org
> >
> > Try https://cms.apache.org/lucene.net/lazy_publish
> > Quick and dirty if it works ;-)
> >
> >
> >
> >   From: Prescott Nasser
> >  <geobmx540@hotmail.com>
> >  To: joe_schaefer@yahoo.com; site-dev@apache.org
> >  Sent: Wednesday, February 15, 2012 1:27 PM
> >  Subject: RE: trouble getting cms content to work correctly
> >
> >
> >
> >
> >
> >
> > I'm sorry :( Please by all means take a stab - I'll do nothing until I
> > hear  back.
> >
> > > Date: Wed, 15 Feb 2012 10:24:46 -0800
> > > From: joe_schaefer@yahoo.com
> > > Subject: Re: trouble getting cms content to work correctly
> > > To: joe_schaefer@yahoo.com; geobmx540@hotmail.com; site-dev@apache.org
> > >
> > > Well I watched your attempt to publish the site and you guys
> > > have managed to break svn merge with too many adds/deletes
> > > of the same paths within a single merge session.  I suggest
> > > you let me fix your site by nuking the publication tree
> > > and copying things over from staging.
> > >
> > >
> > >
> > > ----- Original Message -----
> > > > From:
> >  Joe Schaefer
> >  <joe_schaefer@yahoo.com>
> > > > To:
> >  Prescott Nasser
> >  <geobmx540@hotmail.com>;
> >  "site-dev@apache.org"
> >  <site-dev@apache.org>
> > > >
> >  Cc:
> > > > Sent: Wednesday, February 15, 2012 12:14 PM
> > > > Subject: Re: trouble getting cms content to work correctly
> > > >
> > > >
> > > >
> > > >> ________________________________
> > > >>  From: Prescott Nasser <geobmx540@hotmail.com>
> > > >> To: joe_schaefer@yahoo.com; site-dev@apache.org
> > > >> Sent: Wednesday, February 15, 2012 11:58 AM
> > > >> Subject: RE: trouble getting cms content to work correctly
> > > >>
> > > >>
> > > >>
> > > >> Thanks Joe, I really appreciate your help.
> > > >>
> > > >> My next task was to tackle that doc issue. I was experimenting with
> > the
> > > > upload a
> > > >> tarball option hoping that would reduce the number of files in the
> > repo, but
> > > > I
> > > >> found out all it does is unpack it for me, saves me some bandwidth,
> > but does
> > > >
> >  nothing
> > > >> to save the tree.
> > > >>
> > > >> A couple of weeks ago, I was making no changes to the docs (and there
> > were
> > > > no pending changes that I saw), and just making a minor change to the
> > index page
> > > > (to announce a new version of Lucene.Net) took FOREVER - same timeout
> > issues.
> > > > This lead me to believe, that regardless of the size of the change,
> > the number
> > > > of files will always be a PIA. But it seems like that shouldn't be the
> > case?
> > > >
> > > >
> > > > Hard to say what the cause of that delay was, but I can assure you it
> > had little
> > > > or nothing
> > > > to do with the overall size of your site.  The only O(N) algorithm
> > involved is
> > > > when the build
> > > > system svn up's the tree, and if the changes are already present that
> > > > process shouldn't take
> > > > more
> >  than a handful of seconds even for a 10GB site.  Of course the actual time
> > > > may fluctuate
> > > > wildly due to server conditions on the cms or svn host systems, but
> > there you
> > > > go.
> > > >
> > > >
> > > > I just added some docs about this to the bottom of the
> > > > http://www.apache.org/dev/cmsref page
> > > > you might want to look over.
> > > >
> > > >
> > > >>
> > > >> I will publish what we have now (need to fix a minor issue in the
> > 2.9.4
> > > > documentation first), and give a shot at making a minor change.
> > Hopefully
> > > > publishing just a minor change in that case will be quick and painless.
> > > >
> > > >
> > > > Good luck.  I suggest using the publish.pl script on people.apache.organd
> > > > grabbing a cuppa
> >  coffee
> > > >
> >  while things progress.
> > > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message