-
Notifications
You must be signed in to change notification settings - Fork 260
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
fix: sequence_number should be i64 #1448
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This jives with the documentation: https://learn.microsoft.com/azure/service-bus-messaging/message-sequencing#sequence-number
I think there is also an issue with the
|
Seems that way. According to https://learn.microsoft.com/rest/api/servicebus/message-headers-and-properties,
|
I don't know about your release cycle, hopefully it can be merged and released soon. Thanks |
Careful with those docs, @heaths. They seem to be focused on SBMP, which is a deprecated protocol. You'll want to look at the AMQP protocol guide for Service Bus and the Oasis AMQP 1.0 spec.
|
@Gaelik-git from where did you get the error,
That was due to a deserialization error from Service Bus? What version of the service? |
I am not sure how to find the version I am using of the service. It's a servicebus queue that was just created |
On the php sdk the ttl is also documented as float The servicebus was created using terraform, we are not setting the default_ttl_value so it's using the TimeSpan.MAX as value |
I tought I'd give it a try to check if would break in multiple place to fix this issue :
#1447
It's a breaking change for the api, but it's still better than having the runtime issue I met
Let me know, if you more information
Thanks for the good work on all the crates