Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Technical Question] Additional logging/stack traces from uamqp when switching from azure-iot-hub 2.0.2 to 2.2.2
See original GitHub issueHopefully this makes a bit of sense…
I’m currently dealing with a fairly large Django based project which used the IoT Hub Python libraries to communicate with devices located on an Azure IoT Hub. Last week (specifically on 2020-09-11) we found that our calls to the IoT hub were not working. We eventually discovered that the specific version of the azure-iot-hub library wouldn’t work properly. If we updated the version from 2.02 to 2.2.2, things started working again. But in addition to working, any time we close the local development environment, we get several stack traces, like so:
[repeated ~10 times, with the final two stack traces looking like the following]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "c:\program files\python37\lib\logging\__init__.py", line 1365, in debug
File "c:\program files\python37\lib\logging\__init__.py", line 1621, in isEnabledFor
TypeError: 'NoneType' object is not callable
Exception ignored in: 'uamqp.c_uamqp.XIO.__dealloc__'
Traceback (most recent call last):
File "c:\program files\python37\lib\logging\__init__.py", line 1365, in debug
File "c:\program files\python37\lib\logging\__init__.py", line 1621, in isEnabledFor
TypeError: 'NoneType' object is not callable
Traceback (most recent call last):
File "c:\program files\python37\lib\logging\__init__.py", line 1619, in isEnabledFor
KeyError: None
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "c:\program files\python37\lib\logging\__init__.py", line 1365, in debug
File "c:\program files\python37\lib\logging\__init__.py", line 1621, in isEnabledFor
TypeError: 'NoneType' object is not callable
Exception ignored in: 'uamqp.c_uamqp.XIO.__dealloc__'
Traceback (most recent call last):
File "c:\program files\python37\lib\logging\__init__.py", line 1365, in debug
File "c:\program files\python37\lib\logging\__init__.py", line 1621, in isEnabledFor
TypeError: 'NoneType' object is not callable
It may just be the structure of the application I’m working on, but it seems that something is being de-allocated several times when it has already been de-allocated. The version of uamqp is 1.2.10, which is what was installed when we updated the azure-iot-hub library. Prior to updating to 2.2.2, we didn’t see any such error messages.
Has anyone seen something like this before? If so, any ideas what we can do to resolve this?
AB#8312330
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi @JoelBennett , thanks for all the info! This is helpful, we’re taking a look to see if it’s something that could be an issue with the recent release. Agreed that this should be documented as a best practice/guidelines-- noted. We’ll look at adding this to our Common pitfalls/FAQ page.
@JoelBennett, thank you for your contribution to our open-sourced project! Please help us improve by filling out this 2-minute customer satisfaction survey