-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Celery Monitor no longer works with Django 2.2 #107
Comments
I am having the same issue now. Any updates on this? |
Me too, I have looked quickly at the problem and it seems that select_for_update_or_create is an extension of select_for_update added to the base object manager. We have to rewrite this fonction ! I don't have time to check this now but if no one do, I will try later this month. |
Has anyone found a workaround for this yet? |
@AndrewModus @NerdSec @cryocaustik @stygmate Quick fix... Go to file
|
Seems like the repo is abandoned. @SYNchroACK Why not package & publish using pip? |
I would really love if one of the PRs would merge :( I want to use this project too. |
This is still an issue, any chance of getting a new release out? |
Adding my voice to the chorus. |
Celery Monitor no longer works with Django 2.2:
More specifically:
It looks like it's an issue where the django internal method
_extract_model_params
is no longer returning(lookup, params)
but onlyparams
Link to the django source code (search for
def _extract_model_params
):https://docs.djangoproject.com/en/2.1/_modules/django/db/models/query/
https://docs.djangoproject.com/en/2.2/_modules/django/db/models/query/
The text was updated successfully, but these errors were encountered: