If loop is passed to MQTTClient, previously it was not passed down
to PluginManager, which could potentially grab a different loop from
asyncio.get_event_loop(), resulting in a separate event loop being
created or wrong one being used. Now the loop argument is passed down
as expected.
Coverage remained the same at ?% when pulling af8238e6bf72ba1193eaec0e3b74f964bf602efb on girtsf:master into 8921c792d4e290860ebcbe6524035d3c371cc995 on beerfactory:master.
Coverage remained the same at ?% when pulling af8238e6bf72ba1193eaec0e3b74f964bf602efb on girtsf:master into 8921c792d4e290860ebcbe6524035d3c371cc995 on beerfactory:master.
Coverage remained the same at ?% when pulling af8238e6bf72ba1193eaec0e3b74f964bf602efb on girtsf:master into 8921c792d4e290860ebcbe6524035d3c371cc995 on beerfactory:master.
If
loop
is passed toMQTTClient
, previously it was not passed down toPluginManager
, which could potentially grab a different loop fromasyncio.get_event_loop()
, resulting in a separate event loop being created or wrong one being used. Now theloop
argument is passed down as expected.