Stuck on an issue?

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.

Unhandled error in discovery.py

See original GitHub issue

bleak version: 0.4.2
Python version: 3.6.7
Operating System: Xubuntu 18.04 (4.15.0-50-generic)

Description

Every time I try to list BLE devices (using discover()), bleak lists the devices and prints 20 to 50 times the same beautiful unhandled error.

It seems to appear randomly (1-2 times every 2-5 try).

The function is here.

What I Did

Here’s the error:

Unhandled Error
Traceback (most recent call last):
  File "/home/usr/dir/virtualEnv/lib/python3.6/site-packages/txdbus/protocol.py", line 141, in dataReceived
    self.rawDBusMessageReceived(raw_msg)
  File "/home/usr/dir/virtualEnv/lib/python3.6/site-packages/txdbus/protocol.py", line 262, in rawDBusMessageReceived
    self.signalReceived(m)
  File "/home/usr/dir/virtualEnv/lib/python3.6/site-packages/txdbus/client.py", line 643, in signalReceived
    self.router.routeMessage(msig)
  File "/home/usr/dir/virtualEnv/lib/python3.6/site-packages/txdbus/router.py", line 128, in routeMessage
    r.match(m)
--- <exception caught here> ---
  File "/home/usr/dir/virtualEnv/lib/python3.6/site-packages/txdbus/router.py", line 67, in match
    self.callback(m)
  File "/home/usr/dir/virtualEnv/lib/python3.6/site-packages/bleak/backends/bluezdbus/discovery.py", line 109, in parse_msg
    *_device_info(msg_path, devices.get(msg_path))
  File "/home/usr/dir/virtualEnv/lib/python3.6/site-packages/bleak/backends/bluezdbus/discovery.py", line 39, in _device_info
    name = props.get("Name", props.get("Alias", path.split("/")[-1]))
builtins.AttributeError: 'NoneType' object has no attribute 'get'

Issue Analytics

State:
Created 4 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

hbldhcommented, Jul 1, 2019

Released 0.4.3 yesterday. This is handled better there. Reopen issue if it persists.

0reactions

jollierfinbeancommented, Sep 8, 2019

@jollierfinbean The traceback of the error is only printed now, instead of the application crashing is it not? The printout will disappear as well in version 0.5.1, btw.

Yes, it does not crash. Also thank you for removing the exception logging since it cluttered my logs pretty badly. 👍

Top Results From Across the Web

Ansible - Unhandled error in Python interpreter discovery for

[WARNING]: Unhandled error in Python interpreter discovery for host myubuntuIP: unexpected output from Python interpreter discovery ...

Unhandled error in Python interpreter ... - Google Groups

Hello team. I wanted to ask you for some help with this error when trying to connect to a cisco router from Ansible....

unhandled error in python interpreter discovery - You.com | The ...

Inventory is populating however when running jobs I seem to be having an issue with python interpreter discovery. Also when I try to...

unhandled error in python interpreter discovery for host

unhandled error in python interpreter discovery for host · ansible. · unhandled error in python interpreter discovery for host failed to connect to...

Cloud Storage Errors and Error Handling - App Engine

If you have feedback or questions as you navigate the site, click Send Feedback. Python 2 is no longer supported by the community....