Selwin Ong

What you suggested sounds reasonable, do you mind opening a PR for this?

PR welcome :)

I think this is because variables in https://github.com/rq/django-rq/blob/master/django_rq/settings.py is generated when your project is first run and is cached. I think it'd be easier to add this line to Django's...

@StriveForBest setting `ASYNC` to `False` will run jobs synchronously, but you'll still need Redis, because it will store job information and results in Redis.

Mind opening a PR for this? > On Mar 4, 2021, at 4:17 AM, BobReid wrote: > >  > I just ran into this. > It used to work...

May I know the rationale behind this pull request?

Django's ORM doesn't play well with code that calls `os.fork()` (see https://code.djangoproject.com/ticket/20562) . A workaround for this is to re-open the DB connection every time your function runs. We can...

We used to have a problem where jobs with "get_current_job" would fail , but not ever since we added this line here: https://github.com/ui/django-rq/blob/master/django_rq/management/commands/rqworker.py#L69 Are you getting any errors?

Sorry I wasn't being entirely clear. What I meant is that [we already push](https://github.com/ui/django-rq/blob/master/django_rq/management/commands/rqworker.py#L69) the Redis connection into LocalStack when you run `python manage.py rqworker`. `get_current_job` should just work. Are...

Hold on, why would you want to use get_current_job within runserver command? > On Oct 16, 2013, at 2:04 PM, samuel goldszmidt [email protected] wrote: > > Thx for your answer....