You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Yes. When the package uvloop is installed with SN1, you get an error There is no current event loop in thread 'Thread-4 (run)'.. This occurs because uvloop overrides the asyncio loop functionality and now requires a loop to be defined within the bittensor package.
Describe the solution you'd like
I suggest passing in a loop: asyncio.LoopSetupType into the axon.__init__(...).
Find a way to attach uvicorn server to an existing event loop. This doesn't seem to be supported from what I can find. They did make this change awhile back but was later removed for reasons I haven't been able to determine. The server itself now only takes in loop of type LoopSetupType instead of the AbstractEventLoop type we'd need.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Yes. When the package
uvloop
is installed with SN1, you get an errorThere is no current event loop in thread 'Thread-4 (run)'.
. This occurs becauseuvloop
overrides theasyncio
loop functionality and now requires a loop to be defined within the bittensor package.Describe the solution you'd like
I suggest passing in a
loop: asyncio.LoopSetupType
into theaxon.__init__(...)
.Describe alternatives you've considered
I see a few possible solutions:
axon.py
to useloop="asyncio"
:loop
passed in when anaxon
is initiated:uvicorn
server to an existing event loop. This doesn't seem to be supported from what I can find. They did make this change awhile back but was later removed for reasons I haven't been able to determine. The server itself now only takes inloop
of typeLoopSetupType
instead of theAbstractEventLoop
type we'd need.Additional context
No response
The text was updated successfully, but these errors were encountered: