{5} Assigned, Active Tickets by Owner (Full Description) (3 matches)
List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.
asaddi
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #49 | PATH_INFO & SCRIPT_NAME should be decoded | flup.server | flup.server-1.0.3 | defect | 02/02/10 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
WSGI requires the PATH_INFO & SCRIPT_NAME variables to be decoded. See http://groups.google.com/group/python-web-sig/browse_frm/thread/2003e1c1ecce27b2 and http://wsgi.org/wsgi/WSGI_2.0#decoding-script-name-path-info. I've attached a patch for AJP but the others also probably need to be fixed. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #13 | PreforkServer recreating processes under high load | flup.server | enhancement | 02/21/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I'm trying to take advantage of a 4-way machine using the PreforkServer?. While using up to 4 child processes (1 for each cpu), I'd like the server to return to 1 child after load dies down. Specifically I'm using the scgi_fork server. With these settings: maxSpare=1 maxChildren=4 The number of children jump up to 4 under high load, but the PIDs keep incrementing so I think children are being killed and created while under load. I think that the children should not die until the load drops off. I get much better performance (100% of 4 cpus) with this setting: maxSpare=4 maxChildren=4 But then I've got RAM tied up for no reason. A think that a solution to this is to specify a time to live for excess children. When an excess child has not been used for x seconds, it can be killed. Otherwise it should continue to serve. Randall - randall at tnr dot cc |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #36 | Have WSGIServer warn when someone returns a string from their application | flup.server | enhancement | 12/01/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When someone (dumb, like me) returns a string from the application they pass to WSGIServer, warn the user that it's dumb, and broken. i.e. # super-simple app
def myapp
return "This is my string ... I'm nestled among a big list of other returns, so I'm hard to find."
# instead of
# return ["This makes WSGIServer do happy things"]
# Somewhere in here this should warn ... Returning strings is dumb, and wrong.
WSGIServer(myapp).run()
I just spent 4 hours figuring that out, so I thought I'd share. (I suppose an assert might be grand, especially since you can -O them out) Alternatively, WSGIServer could check to see if it's getting a string, and not interpret it as an interable ... Cheers |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
