Exception Error

[wtf911]

It works but I figured there's something that could be cleaned up somewhere. I get this error every command I run. The command works though.

INFO:pyvizio.cli:
Name    Nickname
------  ----------
CAST    SMARTCAST
HDMI-1  Cable Box
HDMI-2  HDMI-2
HDMI-3  HDMI-3
COMP    COMP
TV      TV
Exception ignored in: <function _ProactorBasePipeTransport.__del__ at 0x00000244C1364790>
Traceback (most recent call last):
  File "c:\python38\lib\asyncio\proactor_events.py", line 116, in __del__
    self.close()
  File "c:\python38\lib\asyncio\proactor_events.py", line 108, in close
    self._loop.call_soon(self._call_connection_lost, None)
  File "c:\python38\lib\asyncio\base_events.py", line 719, in call_soon
    self._check_closed()
  File "c:\python38\lib\asyncio\base_events.py", line 508, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed

[raman325]

Are you running this directly via the CLI or are you running a script/other program that calls these CLI commands? And what command were you running when you saw the above error?

[wtf911]

Windows 10, Python 3.8.2, running it in the Command Prompt. Running it directly by just type pyvizio ...

Any command. Get list, power on, power off.

pyvizio --ip=192.168.1.12 --auth=Zvi4gxey9w get-inputs-list
INFO:pyvizio.cli:
Name Nickname

---

CAST SMARTCAST
HDMI-1 Cable Box
HDMI-2 HDMI-2
HDMI-3 HDMI-3
COMP COMP
TV TV
Exception ignored in: <function _ProactorBasePipeTransport.del at 0x000001A007404790>
Traceback (most recent call last):
File "c:\python38\lib\asyncio\proactor_events.py", line 116, in del
self.close()
File "c:\python38\lib\asyncio\proactor_events.py", line 108, in close
self._loop.call_soon(self._call_connection_lost, None)
File "c:\python38\lib\asyncio\base_events.py", line 719, in call_soon
self._check_closed()
File "c:\python38\lib\asyncio\base_events.py", line 508, in _check_closed
raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed

[raman325]

I did some googling and found this: encode/httpx#914

Looks like an upstream issue. It looks like there's a workaround but I'd rather not implement it and just wait for the upstream fix since this seems to be a Windows specific problem

[wtf911]

Thanks for the quick feedback. Feel free to close this or leave open if you want to track it.