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

MongoDB result backend serialization logic issue #6258

Closed
9 of 18 tasks
enkidulan opened this issue Jul 29, 2020 · 0 comments · Fixed by #6259
Closed
9 of 18 tasks

MongoDB result backend serialization logic issue #6258

enkidulan opened this issue Jul 29, 2020 · 0 comments · Fixed by #6259

Comments

@enkidulan
Copy link
Contributor

enkidulan commented Jul 29, 2020

Checklist

  • I have verified that the issue exists against the master branch of Celery.
  • This has already been asked to the discussion group first.
  • I have read the relevant section in the
    contribution guide
    on reporting bugs.
  • I have checked the issues list
    for similar or identical bug reports.
  • I have checked the pull requests list
    for existing proposed fixes.
  • I have checked the commit log
    to find out if the bug was already fixed in the master branch.
  • I have included all related issues and possible duplicate issues
    in this issue (If there are none, check this box anyway).

Mandatory Debugging Information

  • I have included the output of celery -A proj report in the issue.
    (if you are not able to do this, then at least specify the Celery
    version affected).
  • I have verified that the issue exists against the master branch of Celery.
  • I have included the contents of pip freeze in the issue.
  • I have included all the versions of all the external dependencies required
    to reproduce this bug.

Optional Debugging Information

  • I have tried reproducing the issue on more than one Python version
    and/or implementation.
  • I have tried reproducing the issue on more than one message broker and/or
    result backend.
  • I have tried reproducing the issue on more than one version of the message
    broker and/or result backend.
  • I have tried reproducing the issue on more than one operating system.
  • I have tried reproducing the issue on more than one workers pool.
  • I have tried reproducing the issue with autoscaling, retries,
    ETA/Countdown & rate limits disabled.
  • I have tried reproducing the issue after downgrading
    and/or upgrading Celery and its dependencies.

Related Issues and Possible Duplicates

Related Issues

Possible Duplicates

  • None

Environment & Settings

Celery version:

celery report Output:

Steps to Reproduce

Required Dependencies

  • Minimal Python Version: N/A or Unknown
  • Minimal Celery Version: N/A or Unknown
  • Minimal Kombu Version: N/A or Unknown
  • Minimal Broker Version: N/A or Unknown
  • Minimal Result Backend Version: N/A or Unknown
  • Minimal OS and/or Kernel Version: N/A or Unknown
  • Minimal Broker Client Version: N/A or Unknown
  • Minimal Result Backend Client Version: N/A or Unknown

Python Packages

pip freeze Output:

Other Dependencies

N/A

Minimally Reproducible Test Case

Expected Behavior

store_result uses serializer.

Actual Behavior

store_result ignores serializer, so getting serialization errors for data types that are compatible with chosen serializer.

For more details please refer to tests in #6259

@auvipy auvipy added this to the 4.4.x milestone Jul 30, 2020
auvipy pushed a commit that referenced this issue Jul 30, 2020
* MongoDB: fix serialization issue

* make python2.7 happy

* make python2.7 happy

* make flake8 happy

* use pytest.importorskip

* add myself to CONTRIBUTORS.txt

Co-authored-by: Maksym Shalenyi <mshalenyi@localhost.localdomain>
jeyrce pushed a commit to jeyrce/celery that referenced this issue Aug 25, 2021
* MongoDB: fix serialization issue

* make python2.7 happy

* make python2.7 happy

* make flake8 happy

* use pytest.importorskip

* add myself to CONTRIBUTORS.txt

Co-authored-by: Maksym Shalenyi <mshalenyi@localhost.localdomain>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants