Error: Couldn't get 'time_to_live' about azure-uamqp-python HOT 4 CLOSED

Good catch - I will take a look! Thanks for the report :)

from azure-uamqp-python.

Hi @zach-b - I've just run some tests against a ServiceBus queue and I'm not seeing this error.
What kind of SB entity are you receiving from? What is the message ttl for this entity configured to?

It's likely that we're raising a ValueError instead of just returning None when the header doesn't have the ttl value set - though I'm unsure why SB wouldn't be setting this value on the header.

from azure-uamqp-python.

Hi annatisch, I checked the ttl and turns out I left it to the default when creating a queue through the REST interface, which is actually huge (see https://docs.microsoft.com/en-us/rest/api/servicebus/queues/createorupdate): a bit more than 10675199 days.
Setting it to a more reasonable value made the bug go away.

It seems that the bug occurs when the ttl is too high

from azure-uamqp-python.

Fix published in v0.1.1 :)

from azure-uamqp-python.