Thread: CVS Viewer on Gborg is broken :-(
The CVS viewers on Gborg appear to be broken. From a cursory glance at the logs I cannot see any obvious errors. Anyone know whats wrong? /D
URL? On Tue, 19 Jul 2005, Dave Page wrote: > The CVS viewers on Gborg appear to be broken. From a cursory glance at > the logs I cannot see any obvious errors. > > Anyone know whats wrong? > > /D > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
http://gborg.postgresql.org/project/slony1/cvs/cvs.php Or http://gborg.postgresql.org/project/psqlodbc/cvs/cvs.php Or any other project I assume... /D > -----Original Message----- > From: Marc G. Fournier [mailto:scrappy@postgresql.org] > Sent: 19 July 2005 15:44 > To: Dave Page > Cc: pgsql-www@postgresql.org; Chris Ryan > Subject: Re: [pgsql-www] CVS Viewer on Gborg is broken :-( > > > URL? > > On Tue, 19 Jul 2005, Dave Page wrote: > > > The CVS viewers on Gborg appear to be broken. From a > cursory glance at > > the logs I cannot see any obvious errors. > > > > Anyone know whats wrong? > > > > /D > > > > ---------------------------(end of > broadcast)--------------------------- > > TIP 6: explain analyze is your friend > > > > ---- > Marc G. Fournier Hub.Org Networking Services > (http://www.hub.org) > Email: scrappy@hub.org Yahoo!: yscrappy > ICQ: 7615664 >
'k, Chris is using the chora system from the Horde framework for CVS ... but, from what i can tell, he has everything encapsulated within gborg, so it isn't using anything "external" ... there are no errors being generated anywhere that I can find, not even a SegFault ... but there are no HTML tags being displayed within the cvs.php file either ... Am trying to trace through cvs.php right now, to see if I can figure out where the break is ... On Tue, 19 Jul 2005, Dave Page wrote: > http://gborg.postgresql.org/project/slony1/cvs/cvs.php > > Or > > http://gborg.postgresql.org/project/psqlodbc/cvs/cvs.php > > Or any other project I assume... > > /D > >> -----Original Message----- >> From: Marc G. Fournier [mailto:scrappy@postgresql.org] >> Sent: 19 July 2005 15:44 >> To: Dave Page >> Cc: pgsql-www@postgresql.org; Chris Ryan >> Subject: Re: [pgsql-www] CVS Viewer on Gborg is broken :-( >> >> >> URL? >> >> On Tue, 19 Jul 2005, Dave Page wrote: >> >>> The CVS viewers on Gborg appear to be broken. From a >> cursory glance at >>> the logs I cannot see any obvious errors. >>> >>> Anyone know whats wrong? >>> >>> /D >>> >>> ---------------------------(end of >> broadcast)--------------------------- >>> TIP 6: explain analyze is your friend >>> >> >> ---- >> Marc G. Fournier Hub.Org Networking Services >> (http://www.hub.org) >> Email: scrappy@hub.org Yahoo!: yscrappy >> ICQ: 7615664 >> > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
"Only variable references should be returned by reference" is the cause ... apparently, its a known problem with PHP 4.4.0 ... before downgrading back to 4.3.11, I'm checking to see if there is a 'quick work around' that I can apply to fix the issue temporarily ... if not, will downgrade to 4.3.11 :( On Tue, 19 Jul 2005, Marc G. Fournier wrote: > > 'k, Chris is using the chora system from the Horde framework for CVS ... but, > from what i can tell, he has everything encapsulated within gborg, so it > isn't using anything "external" ... there are no errors being generated > anywhere that I can find, not even a SegFault ... but there are no HTML tags > being displayed within the cvs.php file either ... > > Am trying to trace through cvs.php right now, to see if I can figure out > where the break is ... > > > On Tue, 19 Jul 2005, Dave Page wrote: > >> http://gborg.postgresql.org/project/slony1/cvs/cvs.php >> >> Or >> >> http://gborg.postgresql.org/project/psqlodbc/cvs/cvs.php >> >> Or any other project I assume... >> >> /D >> >>> -----Original Message----- >>> From: Marc G. Fournier [mailto:scrappy@postgresql.org] >>> Sent: 19 July 2005 15:44 >>> To: Dave Page >>> Cc: pgsql-www@postgresql.org; Chris Ryan >>> Subject: Re: [pgsql-www] CVS Viewer on Gborg is broken :-( >>> >>> >>> URL? >>> >>> On Tue, 19 Jul 2005, Dave Page wrote: >>> >>>> The CVS viewers on Gborg appear to be broken. From a >>> cursory glance at >>>> the logs I cannot see any obvious errors. >>>> >>>> Anyone know whats wrong? >>>> >>>> /D >>>> >>>> ---------------------------(end of >>> broadcast)--------------------------- >>>> TIP 6: explain analyze is your friend >>>> >>> >>> ---- >>> Marc G. Fournier Hub.Org Networking Services >>> (http://www.hub.org) >>> Email: scrappy@hub.org Yahoo!: yscrappy >>> ICQ: 7615664 >>> >> > > ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) > Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
> -----Original Message----- > From: Marc G. Fournier [mailto:scrappy@postgresql.org] > Sent: 19 July 2005 16:19 > To: Marc G. Fournier > Cc: Dave Page; pgsql-www@postgresql.org; Chris Ryan > Subject: RE: [pgsql-www] CVS Viewer on Gborg is broken :-( > > > "Only variable references should be returned by reference" > > is the cause ... apparently, its a known problem with PHP 4.4.0 ... > before downgrading back to 4.3.11, I'm checking to see if there is a > 'quick work around' that I can apply to fix the issue > temporarily ... if > not, will downgrade to 4.3.11 :( Oh, so it got upgraded then? Was that before or after it started segfaulting? /D
On Tue, 19 Jul 2005, Dave Page wrote: > > >> -----Original Message----- >> From: Marc G. Fournier [mailto:scrappy@postgresql.org] >> Sent: 19 July 2005 16:19 >> To: Marc G. Fournier >> Cc: Dave Page; pgsql-www@postgresql.org; Chris Ryan >> Subject: RE: [pgsql-www] CVS Viewer on Gborg is broken :-( >> >> >> "Only variable references should be returned by reference" >> >> is the cause ... apparently, its a known problem with PHP 4.4.0 ... >> before downgrading back to 4.3.11, I'm checking to see if there is a >> 'quick work around' that I can apply to fix the issue >> temporarily ... if >> not, will downgrade to 4.3.11 :( > > Oh, so it got upgraded then? Was that before or after it started > segfaulting? After, that was why I did the upgrade, to clean that stuff up ... but the *old* horde stuff has some bad code in it that the newer horde stuff has already fixed, and Chris has some ancient horde stuff in place :( ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
I looked at updagrading to a newer version of Horde at one point but they had changed their architecture in some way that wasn't compatible with the way I was incorporating the CVS code. The incorporation has always been the tricky part. Setting up something that wasn't incorporated wouldn't be too much trouble if we wanted to try and work with newer stuff. Chris --- "Marc G. Fournier" <scrappy@postgresql.org> wrote: > On Tue, 19 Jul 2005, Dave Page wrote: > > > Oh, so it got upgraded then? Was that before or after it started > > segfaulting? > > After, that was why I did the upgrade, to clean that stuff up ... but > the > *old* horde stuff has some bad code in it that the newer horde stuff > has > already fixed, and Chris has some ancient horde stuff in place :( __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Is there a reason against using something like the perl one we use on the main site, and, I believe, on pgfoundry? instead of the horde stuff? So far, the only problems we've had reported with php4.4.0 have been horde related issues, so I'm really loath to downgrade if we can help it :( From what I can read in the release notes, the "cause" of the problem is a fix they did to the API to eliminate some memory leakage ... which is also why the bump'd the second # from 3->4 :( On Tue, 19 Jul 2005, Chris Ryan wrote: > I looked at updagrading to a newer version of Horde at one point > but they had changed their architecture in some way that wasn't > compatible with the way I was incorporating the CVS code. The > incorporation has always been the tricky part. Setting up something > that wasn't incorporated wouldn't be too much trouble if we wanted to > try and work with newer stuff. > > Chris > > --- "Marc G. Fournier" <scrappy@postgresql.org> wrote: >> On Tue, 19 Jul 2005, Dave Page wrote: >> >>> Oh, so it got upgraded then? Was that before or after it started >>> segfaulting? >> >> After, that was why I did the upgrade, to clean that stuff up ... but >> the >> *old* horde stuff has some bad code in it that the newer horde stuff >> has >> already fixed, and Chris has some ancient horde stuff in place :( > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
One of the reasons Horde was choosen was because it was PHP and made the inegration easier. If we just want to stand something up without integrating completely then we can use anything we want. Before Horde was integrated a python based viewcvs was used in the early days. Chris --- "Marc G. Fournier" <scrappy@postgresql.org> wrote: > > Is there a reason against using something like the perl one we use on > the > main site, and, I believe, on pgfoundry? instead of the horde stuff? > > So far, the only problems we've had reported with php4.4.0 have been > horde > related issues, so I'm really loath to downgrade if we can help it :( > > From what I can read in the release notes, the "cause" of the problem > is a > fix they did to the API to eliminate some memory leakage ... which is > also > why the bump'd the second # from 3->4 :( > > > > On Tue, 19 Jul 2005, Chris Ryan wrote: > > > I looked at updagrading to a newer version of Horde at one point > > but they had changed their architecture in some way that wasn't > > compatible with the way I was incorporating the CVS code. The > > incorporation has always been the tricky part. Setting up something > > that wasn't incorporated wouldn't be too much trouble if we wanted > to > > try and work with newer stuff. > > > > Chris > > > > --- "Marc G. Fournier" <scrappy@postgresql.org> wrote: > >> On Tue, 19 Jul 2005, Dave Page wrote: > >> > >>> Oh, so it got upgraded then? Was that before or after it started > >>> segfaulting? > >> > >> After, that was why I did the upgrade, to clean that stuff up ... > but > >> the > >> *old* horde stuff has some bad code in it that the newer horde > stuff > >> has > >> already fixed, and Chris has some ancient horde stuff in place :( > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com > > > > ---- > Marc G. Fournier Hub.Org Networking Services > (http://www.hub.org) > Email: scrappy@hub.org Yahoo!: yscrappy ICQ: > 7615664 > ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
How hard would it be to put in a standalone one as a temporary fix, so that 'fixing' the horde one isn't too panick'd? On Tue, 19 Jul 2005, Chris Ryan wrote: > One of the reasons Horde was choosen was because it was PHP and > made the inegration easier. If we just want to stand something up > without integrating completely then we can use anything we want. Before > Horde was integrated a python based viewcvs was used in the early days. > > Chris > > --- "Marc G. Fournier" <scrappy@postgresql.org> wrote: > >> >> Is there a reason against using something like the perl one we use on >> the >> main site, and, I believe, on pgfoundry? instead of the horde stuff? >> >> So far, the only problems we've had reported with php4.4.0 have been >> horde >> related issues, so I'm really loath to downgrade if we can help it :( >> >> From what I can read in the release notes, the "cause" of the problem >> is a >> fix they did to the API to eliminate some memory leakage ... which is >> also >> why the bump'd the second # from 3->4 :( >> >> >> >> On Tue, 19 Jul 2005, Chris Ryan wrote: >> >>> I looked at updagrading to a newer version of Horde at one point >>> but they had changed their architecture in some way that wasn't >>> compatible with the way I was incorporating the CVS code. The >>> incorporation has always been the tricky part. Setting up something >>> that wasn't incorporated wouldn't be too much trouble if we wanted >> to >>> try and work with newer stuff. >>> >>> Chris >>> >>> --- "Marc G. Fournier" <scrappy@postgresql.org> wrote: >>>> On Tue, 19 Jul 2005, Dave Page wrote: >>>> >>>>> Oh, so it got upgraded then? Was that before or after it started >>>>> segfaulting? >>>> >>>> After, that was why I did the upgrade, to clean that stuff up ... >> but >>>> the >>>> *old* horde stuff has some bad code in it that the newer horde >> stuff >>>> has >>>> already fixed, and Chris has some ancient horde stuff in place :( >>> >>> >>> __________________________________________________ >>> Do You Yahoo!? >>> Tired of spam? Yahoo! Mail has the best spam protection around >>> http://mail.yahoo.com >>> >> >> ---- >> Marc G. Fournier Hub.Org Networking Services >> (http://www.hub.org) >> Email: scrappy@hub.org Yahoo!: yscrappy ICQ: >> 7615664 >> > > > > > ____________________________________________________ > Start your day with Yahoo! - make it your home page > http://www.yahoo.com/r/hs > > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
I'll put something up as soon as I get back. If anyone wants to make a suggestion of something that would be easy and functional to get going that would be great as it's been a long time since i've been in the market for cvs viewers. Chris --- "Marc G. Fournier" <scrappy@postgresql.org> wrote: > > How hard would it be to put in a standalone one as a temporary fix, > so > that 'fixing' the horde one isn't too panick'd? > > On Tue, 19 Jul 2005, Chris Ryan wrote: > > > One of the reasons Horde was choosen was because it was PHP and > > made the inegration easier. If we just want to stand something up > > without integrating completely then we can use anything we want. > Before > > Horde was integrated a python based viewcvs was used in the early > days. > > > > Chris > > > > --- "Marc G. Fournier" <scrappy@postgresql.org> wrote: > > > >> > >> Is there a reason against using something like the perl one we use > on > >> the > >> main site, and, I believe, on pgfoundry? instead of the horde > stuff? > >> > >> So far, the only problems we've had reported with php4.4.0 have > been > >> horde > >> related issues, so I'm really loath to downgrade if we can help it > :( > >> > >> From what I can read in the release notes, the "cause" of the > problem > >> is a > >> fix they did to the API to eliminate some memory leakage ... which > is > >> also > >> why the bump'd the second # from 3->4 :( > >> > >> > >> > >> On Tue, 19 Jul 2005, Chris Ryan wrote: > >> > >>> I looked at updagrading to a newer version of Horde at one > point > >>> but they had changed their architecture in some way that wasn't > >>> compatible with the way I was incorporating the CVS code. The > >>> incorporation has always been the tricky part. Setting up > something > >>> that wasn't incorporated wouldn't be too much trouble if we > wanted > >> to > >>> try and work with newer stuff. > >>> > >>> Chris > >>> > >>> --- "Marc G. Fournier" <scrappy@postgresql.org> wrote: > >>>> On Tue, 19 Jul 2005, Dave Page wrote: > >>>> > >>>>> Oh, so it got upgraded then? Was that before or after it > started > >>>>> segfaulting? > >>>> > >>>> After, that was why I did the upgrade, to clean that stuff up > ... > >> but > >>>> the > >>>> *old* horde stuff has some bad code in it that the newer horde > >> stuff > >>>> has > >>>> already fixed, and Chris has some ancient horde stuff in place > :( > >>> > >>> > >>> __________________________________________________ > >>> Do You Yahoo!? > >>> Tired of spam? Yahoo! Mail has the best spam protection around > >>> http://mail.yahoo.com > >>> > >> > >> ---- > >> Marc G. Fournier Hub.Org Networking Services > >> (http://www.hub.org) > >> Email: scrappy@hub.org Yahoo!: yscrappy > ICQ: > >> 7615664 > >> > > > > > > > > > > ____________________________________________________ > > Start your day with Yahoo! - make it your home page > > http://www.yahoo.com/r/hs > > > > > > ---- > Marc G. Fournier Hub.Org Networking Services > (http://www.hub.org) > Email: scrappy@hub.org Yahoo!: yscrappy ICQ: > 7615664 > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
I got a replacement in. I took advantage of the cvsweb.cgi that was preinstalled on the system and made some tweaks to gborg to get it to redirect there when someone tries to access the cvs code. It's not pretty but its working. Chris --- "Marc G. Fournier" <scrappy@postgresql.org> wrote: > > How hard would it be to put in a standalone one as a temporary fix, > so > that 'fixing' the horde one isn't too panick'd? > > On Tue, 19 Jul 2005, Chris Ryan wrote: > > > One of the reasons Horde was choosen was because it was PHP and > > made the inegration easier. If we just want to stand something up > > without integrating completely then we can use anything we want. > Before > > Horde was integrated a python based viewcvs was used in the early > days. > > > > Chris > > > > --- "Marc G. Fournier" <scrappy@postgresql.org> wrote: > > > >> > >> Is there a reason against using something like the perl one we use > on > >> the > >> main site, and, I believe, on pgfoundry? instead of the horde > stuff? > >> > >> So far, the only problems we've had reported with php4.4.0 have > been > >> horde > >> related issues, so I'm really loath to downgrade if we can help it > :( > >> > >> From what I can read in the release notes, the "cause" of the > problem > >> is a > >> fix they did to the API to eliminate some memory leakage ... which > is > >> also > >> why the bump'd the second # from 3->4 :( > >> > >> > >> > >> On Tue, 19 Jul 2005, Chris Ryan wrote: > >> > >>> I looked at updagrading to a newer version of Horde at one > point > >>> but they had changed their architecture in some way that wasn't > >>> compatible with the way I was incorporating the CVS code. The > >>> incorporation has always been the tricky part. Setting up > something > >>> that wasn't incorporated wouldn't be too much trouble if we > wanted > >> to > >>> try and work with newer stuff. > >>> > >>> Chris > >>> > >>> --- "Marc G. Fournier" <scrappy@postgresql.org> wrote: > >>>> On Tue, 19 Jul 2005, Dave Page wrote: > >>>> > >>>>> Oh, so it got upgraded then? Was that before or after it > started > >>>>> segfaulting? > >>>> > >>>> After, that was why I did the upgrade, to clean that stuff up > ... > >> but > >>>> the > >>>> *old* horde stuff has some bad code in it that the newer horde > >> stuff > >>>> has > >>>> already fixed, and Chris has some ancient horde stuff in place > :( > >>> > >>> > >>> __________________________________________________ > >>> Do You Yahoo!? > >>> Tired of spam? Yahoo! Mail has the best spam protection around > >>> http://mail.yahoo.com > >>> > >> > >> ---- > >> Marc G. Fournier Hub.Org Networking Services > >> (http://www.hub.org) > >> Email: scrappy@hub.org Yahoo!: yscrappy > ICQ: > >> 7615664 > >> > > > > > > > > > > ____________________________________________________ > > Start your day with Yahoo! - make it your home page > > http://www.yahoo.com/r/hs > > > > > > ---- > Marc G. Fournier Hub.Org Networking Services > (http://www.hub.org) > Email: scrappy@hub.org Yahoo!: yscrappy ICQ: > 7615664 > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
> -----Original Message----- > From: Chris Ryan [mailto:xgbe@yahoo.com] > Sent: 20 July 2005 02:13 > To: Marc G. Fournier > Cc: Dave Page; pgsql-www@postgresql.org > Subject: RE: [pgsql-www] CVS Viewer on Gborg is broken :-( > > I got a replacement in. I took advantage of the > cvsweb.cgi that was > preinstalled on the system and made some tweaks to gborg to get it to > redirect there when someone tries to access the cvs code. It's not > pretty but its working. Thanks Chris - the cvs viewer is invaluable imho. Regards, Dave.