This operation would block forever about django-websocket-redis HOT 10 CLOSED

I tried an example where the incoming request is of type WSGI ( no websockets), and its still fails alternatively. With the same error.

from django-websocket-redis.

Is your project available on Github or alternatives?
How can you route it into the websocket handler then - that's weird!

from django-websocket-redis.

No its not available, unfortunately. Its a project that I've been working
on at my workplace for a year now. I can create a sample project and see if
I get the same error. If I do I'll post that project on github.

On Fri, Jan 3, 2014 at 11:06 AM, Jacob Rief [email protected]:

Is your project available on Github or alternatives?
How can you route it into the websocket handler then - that's weird!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-31536502
.

from django-websocket-redis.

Apparently you are using websockets for Redis in debug mode, ie. you run it as ./manage runserver instead of uwsgi. Is this correct?

For me it seems, as if line 5 in wsgi_server.py does not work well in debug mode. Try to deactivate this line (only for debug) until I found a fix for it.

from django-websocket-redis.

Thank you for the feedback. And yes I have been using it in debug mode
On Jan 3, 2014 3:49 PM, "Jacob Rief" [email protected] wrote:

Apparently you are using websockets for Redis in debug mode, ie. you run
it as ./manage runserver instead of uwsgi. Is this correct?

For me it seems, as if line 5 in wsgi_server.py does not work well in
debug mode. Try to deactivate this line (only for debug) until I found a
fix for it.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-31556528
.

from django-websocket-redis.

I tried what you suggested. Its still giving me the same error.

from django-websocket-redis.

Somehow I was able to repeat your problem. I therefore moved the monkey patching of redis from the main server to the uwsgi server. I assume/hope that this will fix your problem. Please wait for version 0.2.2 and then try again.

from django-websocket-redis.

Thank you. I appreciate it. I will keep you posted after the next release,
regardless if there is a problem or not.
On Jan 4, 2014 3:57 PM, "Jacob Rief" [email protected] wrote:

Somehow I was able to repeat your problem. I therefore moved the monkey
patching of redis from the main server to the uwsgi server. I assume/hope
that this will fix your problem. Please wait for version 0.2.2 and then try
again.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-31589741
.

from django-websocket-redis.

0.2.2 is available on PyPI.

from django-websocket-redis.

Perfect!! This new release seemed to solve the problem.

from django-websocket-redis.