-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
error when pickle ServiceBusReceivedMessage object #27947
Comments
Thank you the feedback @IsmaelJS. We will investigate and get back to you asap |
Hi @IsmaelJS - I've just tried running the provided sample and am not seeing this error. We've had pickling issues in the past due to some objects in the underlying Would you be able to provide the |
Hi @swathipil , I have updated the serialization error because the old one corresponds to azure-servicebus==7.9.0a1. The error raised is the following:
The lib version are:
Thank you so much. |
Hi @IsmaelJS - Can you provide an example of data sent here that results in this error? I believe I'm not able to reproduce using this sample b/c the data I'm sending and receiving doesn't result in the creation of the |
Hi @swathipil , I have updated the code within "To Reproduce" section with the data used. |
is there any update about it ? |
Hi @IsmaelJS - Thanks for the update and your patience! We were able to reproduce this issue. Releasing We will keep you updated as we move forward! |
Hi @IsmaelJS , @suranshu-engg-segg we will be releasing a new version of the service bus client this week that uses the pure python based AMQP library which should address the pickling issues. Ill update this issue once its on pypi |
Hi @IsmaelJS, @suranshu-engg-segg - We just released azure-servicebus 7.10.0, which includes the fix for pickling ServiceBusReceivedMessage. https://pypi.org/project/azure-servicebus/7.10.0/ Thanks! |
Hi @IsmaelJS. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation. |
Describe the bug
There is an error when trying to pickle the ServiceBusReceivedMessage object.
The "prefork" pool (multiprocessing) in celery uses pickle for serialization, and from v5.2 it is not working, see details in celery/celery#7237
To Reproduce
It can be reproduced by using the following code:
The result is:
Expected behavior
It should works.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
There are several bugs opened in celery and billiard which might be related to this issue:
celery/celery#7237
celery/billiard#356
The text was updated successfully, but these errors were encountered: