Re: Deadlock bug in logging? Reproducible case

2020-04-24 Thread Brian Tiemann
Nah, I'm good — but thank you! On Friday, April 24, 2020 at 8:57:09 AM UTC-4, René Fleschenberg wrote: > > Hi, > > On 4/23/20 12:20 PM, Adam Johnson wrote: > > What version of Python René? > > I tested with 3.6.7. I can test with other versions, if that helps. > > Regards, > René > > > > --

Re: Deadlock bug in logging? Reproducible case

2020-04-23 Thread Brian Tiemann
True, I did notice it needed some more tweaking. I've got a long evening of rewriting years' worth of wsgi.py's and Apache configs ahead of me. I'll probably just jump straight to the envparse approach because (as you noted) my celery env var handling was making the WSGI approach moot anyway. N

Re: Deadlock bug in logging? Reproducible case

2020-04-23 Thread Brian Tiemann
Beautiful. That does the trick. Thank you! And I certainly can see there's plenty of other approaches such as envparse or django-environ that I could be using, that keeps the vars out of my Apache config. Quick fix and a slighly longer better fix. This'll change how I do all my new projects fro

Re: Deadlock bug in logging? Reproducible case

2020-04-23 Thread Brian Tiemann
FYI, here's where that approach came from -- http://ericplumb.com/blog/passing-apache-environment-variables-to-django-via-mod_wsgi.html > > It's the top hit for "django apache environment variable" Which is literally an old friend of mine from grade school. Maybe that's a red flag ... -- You

Re: Deadlock bug in logging? Reproducible case

2020-04-23 Thread Brian Tiemann
ading.py", > line 932 in _bootstrap_inner > File "/Users/chainz/.pyenv/versions/3.8.2/lib/python3.8/threading.py", > line 890 in _bootstrap > > This stood out to me. I checked your wsgi.py , it contained: > > def application(environ, start_response): > retu

Re: Deadlock bug in logging? Reproducible case

2020-04-23 Thread Brian Tiemann
Tom > > On 23 Apr 2020, at 12:40, Brian Tiemann > > wrote: > > It also happens in 3.6.9, which is my prod environment. > > FWIW, by way of background context, this is not a heavily used app, not > enough so to warrant logging to a custom buffered consumer or remote age

Re: Deadlock bug in logging? Reproducible case

2020-04-23 Thread Brian Tiemann
mportant, in other words; it's that the whole app is wedging just because I happen to have a vanilla LOGGING setup configured. On Thursday, April 23, 2020 at 7:02:11 AM UTC-4, Brian Tiemann wrote: > > Hi — Thanks for looking into this. Adam, I skipped over details like the > Python v

Re: Deadlock bug in logging? Reproducible case

2020-04-23 Thread Brian Tiemann
/issue6721 , suggesting this was to do with thread locking. But I'm not qualified to make that call for sure, so I don't want to throw red herrings into the mix. If "standstill" is a better term for this that's what I'll use. Thanks again. On Wednesday, April 22,

Deadlock bug in logging? Reproducible case

2020-04-22 Thread Brian Tiemann
Hi all, I was directed here after getting corroboration on #django and elsewhere. I have what appears to be a bug in which a Django app can deadlock if you hit it with a lot (>3) of AJAX requests within a short time (i.e. all triggered in parallel from a single HTML page). I have a reproducible