Remy Blank | 1 Oct 01:41 2008
Picon

[Trac-dev] Re: Resource Meta Data

Christian Boos wrote:
> In fact, I'd be interested to know who else actually thinks that:
> "
> 
> This kind of generic data storage system just
> doesn't fit with the Trac design philosophy.
> 
> "

I'm quite new around here, so I'm not sure I really know what the "Trac
design philosophy" is. But my reply to the above is: why not? If it
makes the code cleaner and more elegant, and the performance is
adequate, and it provides a solution to a real problem, then I'm all for it.

More important to me than whether or not to introduce such a
functionality is *how* to introduce it. I tend to dislike large,
disruptive changes, and prefer incremental improvement and refactoring.
So if the above can be done incrementally, for example starting on one
or two modules, then refined and propagated step by step to other
modules, then I'm in.

-- Remy

Robert C Corsaro | 1 Oct 12:21 2008

[Trac-dev] Re: Resource Meta Data


Remy Blank wrote:
> Christian Boos wrote:
>> In fact, I'd be interested to know who else actually thinks that:
>> "
>>
>> This kind of generic data storage system just
>> doesn't fit with the Trac design philosophy.
>>
>> "
> 
> I'm quite new around here, so I'm not sure I really know what the "Trac
> design philosophy" is. But my reply to the above is: why not? If it
> makes the code cleaner and more elegant, and the performance is
> adequate, and it provides a solution to a real problem, then I'm all for it.
> 
> More important to me than whether or not to introduce such a
> functionality is *how* to introduce it. I tend to dislike large,
> disruptive changes, and prefer incremental improvement and refactoring.
> So if the above can be done incrementally, for example starting on one
> or two modules, then refined and propagated step by step to other
> modules, then I'm in.

Has anyone bothered to review the code?  I think it's quite nice.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
(Continue reading)

Remy Blank | 1 Oct 12:38 2008
Picon

[Trac-dev] Re: Resource Meta Data

Robert C Corsaro wrote:
> Has anyone bothered to review the code?  I think it's quite nice.

Yes, I have, but not enough in detail to be able to post a review.

My comments were not related to this specific implementation, though,
but to the general comment about a "generic data storage system fitting
the Trac design philosophy".

-- Remy

rupert.thurner@gmail.com | 1 Oct 19:13 2008
Picon

[Trac-dev] Re: Resource Meta Data


On Sep 30, 10:53 am, Catalin Balan <catalin.ba... <at> gmail.com> wrote:
> Hi trac-dev,
>
> In case anyone is still interested in this issue, I have it implemented
> here: [1]
> WikiToolsPlugin provides a set of features like wiki custom fields and
> page/resource relation, based on resource tools.
>
> Some feedback would be very nice.
>
> [1]http://code.optaros.com/svn/oforge/trunk/plugins/resourcetoolsplugin/
> [2]http://code.optaros.com/svn/oforge/trunk/plugins/wikitoolsplugin/
>
> ps. No documentation yet available, since this feature is still under
> development.
>
> Thank you,
> Catalin Balan

it like the code. the features we lack here are:
 * simple fine grained access control on wiki pages, maybe like
   http://moinmo.in/HelpOnAccessControlLists
   (people like to use the wiki as scratchbook and note their not-so-
important passwords ...)
 * some "sign off" or "quality mark" which somehow works like
mediawiki stable versions
 * language the page is written in

for hierarchical wiki page organization i think the url solution would
(Continue reading)

Omry Yadan | 2 Oct 07:47 2008
Picon

[Trac-dev] wsgi + trac + rouge bots = apache down?

Hi all,

here is the deal:

my apache server reached the maximum limit for workers several times in
the last week.

every time I had to restart it, and it bought me 10-20 hours, till the
next incident.

I setup mod_status with extended information, and ran a script that
fetched it every minute to see what is the server status before the
problem appears.

my server didn't disappoint and I got the problem 3-4 hours after I
setup this.

it appears that trac is leaking apache workers.

my trac is configured with wsgi, and it looks like when there is a
certain trac error (any trac error?) the request does not terminate
properly.

with wild and stupid bots out there, this is a recipe for a disaster.

attached is the output of the extended log. you can see that 143
requests are being served at once, all from the firestats.cc vhost (let
me assure you that my site is no where near that popular).

looking at the trac log, I can see many errors like:
(Continue reading)

Graham Dumpleton | 2 Oct 09:19 2008
Picon

[Trac-dev] Re: wsgi + trac + rouge bots = apache down?


On Oct 2, 3:47 pm, Omry Yadan <o... <at> yadan.net> wrote:
> Hi all,
>
> here is the deal:
>
> my apache server reached the maximum limit for workers several times in
> the last week.
>
> every time I had to restart it, and it bought me 10-20 hours, till the
> next incident.
>
> I setup mod_status with extended information, and ran a script that
> fetched it every minute to see what is the server status before the
> problem appears.
>
> my server didn't disappoint and I got the problem 3-4 hours after I
> setup this.
>
> it appears that trac is leaking apache workers.
>
> my trac is configured with wsgi, and it looks like when there is a
> certain trac error (any trac error?) the request does not terminate
> properly.
>
> with wild and stupid bots out there, this is a recipe for a disaster.
>
> attached is the output of the extended log. you can see that 143
> requests are being served at once, all from the firestats.cc vhost (let
> me assure you that my site is no where near that popular).
(Continue reading)

Graham Dumpleton | 2 Oct 09:49 2008
Picon

[Trac-dev] Re: wsgi + trac + rouge bots = apache down?


On Oct 2, 5:25 pm, Omry Yadan <o... <at> yadan.net> wrote:
> > Please clarify your hosting configuration. What do you mean by WSGI?
>
> > Do you mean, running Trac under Apache/mod_wsgi?
>
> > Or do you mean, running tracd and proxying Apache through to tracd?
>
> > Or do you mean, running Trac under some other WSGI server and proxying
> > Apache through to that WSGI server instance?
>
> > The link you give for mod_status doesn't work, at least via Google
> > groups.
>
> using mod_wsgi in apache2.

But what version of mod_wsgi. Make sure you are using version 2.3 if
using older version.

> this is my vhost file :
>
> IWSGIDaemonProcess firestats.cc user=omry group=omry threads=25
> maximum-requests=100

I would use more than 100 requests for maximum-requests unless the
memory leaks in your application are quite bad. Value of 1000 would be
more reasonable.

If you are use mod_wsgi 2.X, there is a deadlock timeout of 300
seconds and so if the whole process was being deadlocked by problem
(Continue reading)

lei | 2 Oct 12:05 2008
Picon

[Trac-dev] Re: Conditiona Field Plugin for 0.11.x


Hi Joshua,

I would suggest publishing your 0.11 version on the same page with the
existing plugin (http://trac-hacks.org/wiki/CondFieldsPlugin), because
that's what it is, a 0.11 version of a plugin allowing conditional
fields. State that there are changes in configuration for this
version, and it should be fine.

Regards, Lucas

On Sep 29, 2:10 pm, "Schmiedlin, Joshua" <jschm... <at> harris.com> wrote:
> Hello All,
>
> I believe this is my first posting, although I have been following this
> group for over a year now.
>
> My managers have expressed an interest in having conditional fields for
> tickets in Trac.  I know there was a plugin written by coderanger/Noah
> for 0.10.x, but it was never ported to 0.11.  Rather than wait for
> someone else to do it I wrote my own for 0.11.  It modifies the Genshi
> stream slightly when loading a ticket.html page.  After that it uses
> jquery to perform hide and show operations on the various elements
> related to ticket fields.  I'm not a web programmer by trade, so I may
> not have done all this in the best way possible, but it seems to work
> like a champ in both FF3 and IE6.
>
> So my question is this...  There already exists a plugin on Trac-hacks.
> My plugin uses different config syntax, so it is slightly different from
> an end-users perspective.  Should I simply create my own trac-hack page
(Continue reading)

Graham Dumpleton | 2 Oct 13:14 2008
Picon

[Trac-dev] Re: wsgi + trac + rouge bots = apache down?


For reference, also see:

 https://www.coderesort.com/about/blog/sporadic_hang_solved

This was mention on #trac. Not sure if that was by you or you were
part of conversation.

Graham

On Oct 2, 5:49 pm, Graham Dumpleton <Graham.Dumple... <at> gmail.com>
wrote:
> On Oct 2, 5:25 pm, Omry Yadan <o... <at> yadan.net> wrote:
>
> > > Please clarify your hosting configuration. What do you mean by WSGI?
>
> > > Do you mean, running Trac under Apache/mod_wsgi?
>
> > > Or do you mean, running tracd and proxying Apache through to tracd?
>
> > > Or do you mean, running Trac under some other WSGI server and proxying
> > > Apache through to that WSGI server instance?
>
> > > The link you give for mod_status doesn't work, at least via Google
> > > groups.
>
> > using mod_wsgi in apache2.
>
> But what version of mod_wsgi. Make sure you are using version 2.3 if
> using older version.
(Continue reading)

Schmiedlin, Joshua | 2 Oct 15:21 2008

[Trac-dev] Re: Conditiona Field Plugin for 0.11.x


Thanks for your input.  I'll do that then. 

-----Original Message-----
From: trac-dev <at> googlegroups.com [mailto:trac-dev <at> googlegroups.com] On
Behalf Of lei <at> mms-dresden.de
Sent: Thursday, October 02, 2008 6:05 AM
To: Trac Development
Subject: [Trac-dev] Re: Conditiona Field Plugin for 0.11.x

Hi Joshua,

I would suggest publishing your 0.11 version on the same page with the
existing plugin (http://trac-hacks.org/wiki/CondFieldsPlugin), because
that's what it is, a 0.11 version of a plugin allowing conditional
fields. State that there are changes in configuration for this
version, and it should be fine.

Regards, Lucas

On Sep 29, 2:10 pm, "Schmiedlin, Joshua" <jschm... <at> harris.com> wrote:
> Hello All,
>
> I believe this is my first posting, although I have been following
this
> group for over a year now.
>
> My managers have expressed an interest in having conditional fields
for
> tickets in Trac.  I know there was a plugin written by coderanger/Noah
(Continue reading)


Gmane