You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2019. It is now read-only.
The documentation states that "default behaviour is to block indefinitely while waiting for a job," but that doesn't seem to happening. Instead job.get seems to be an async call, even when timeout is 0. I'm using [email protected], [email protected], and redis 2.4.2.
The text was updated successfully, but these errors were encountered:
OK, so if the timeout is set to 0 the callback will never be called? How is that useful? (Not being snarky, just trying to understand.) If I want a process to sit and wait for jobs, handling them as they come in, how should I do that?
The documentation states that "default behaviour is to block indefinitely while waiting for a job," but that doesn't seem to happening. Instead job.get seems to be an async call, even when timeout is 0. I'm using [email protected], [email protected], and redis 2.4.2.
The text was updated successfully, but these errors were encountered: