Skip to content
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

Added the CELERY_RESULT_EXTENDED setting and set to True #1104

Merged
merged 1 commit into from
Oct 26, 2022

Conversation

vanbuiten
Copy link
Member

Description

The CELERY_RESULT_EXTENDED setting is added and set to True. This will add the missing information to the database. This is a known issue in release 2.4.0 see celery/django-celery-results#326

Checklist

  • Keep the PR, and the amount of commits to a minimum
  • The commit messages are meaningful and descriptive
  • The change/fix is well documented, particularly in hard-to-understand areas of the code / unit tests
  • Check that the branch is based on master and is up to date with master
  • Check that the PR targets master
  • There are no merge conflicts and no conflicting Django migrations

How has this been tested?

  • Tested the change/fix locally and all unit tests still pass
  • Code coverage is at least 85% (the higher the better)
  • No iSort, Flake8 and SPDX issues are present in the code

add the missing information to the database. This is a known issue in release
2.4.0 see celery/django-celery-results#326
@vanbuiten vanbuiten requested a review from tcoenen October 26, 2022 07:50
@vanbuiten vanbuiten self-assigned this Oct 26, 2022
Copy link
Contributor

@tcoenen tcoenen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Akkoord!

@vanbuiten vanbuiten merged commit 25b5ef8 into master Oct 26, 2022
@vanbuiten vanbuiten deleted the chore/add-celery_result_extended-to-settings branch October 26, 2022 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants