Getting "RuntimeError: Task got Future <Future pending> attached to a different loop" on Windows about metricity HOT 4 CLOSED

bit of a long shot, but could you try adding this to the dunder init before anything asyncio related is called. We had to do this in the bots for aiodns on windows, might work here too.

if os.name == "nt":
    asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())

from metricity.

bit of a long shot, but could you try adding this to the dunder init before anything asyncio related is called. We had to do this in the bots for aiodns on windows, might work here too.

if os.name == "nt":
    asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())

That didn't seem to make a difference

from metricity.

bit of a long shot, but could you try adding this to the dunder init before anything asyncio related is called. We had to do this in the bots for aiodns on windows, might work here too.

if os.name == "nt":
    asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())

That didn't seem to make a difference

I'll take a look at it later.

from metricity.

This was because d.py was set to master branch in pyproject.toml, rather than being pinned to a specific version.

The recent asyncio changes in d.py made it incompatible with our current setup.

In the linked PR I pinned d.py to a version before those changes.

from metricity.