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
{{ message }}
This repository has been archived by the owner on Mar 6, 2024. It is now read-only.
I'm not sure if I should make an issue here, or in discord.py, but basically I'm using Llama Indexrun-llama on GitHub, and it uses nest_asyncio for the event loop patching. Issue is, when I run it alongside discord.py, random things will be put into seemingly random event loops and I'm not sure why? Like for instance when the bot runs startup it checks the guilds it's in and then checks the indexed channels in order to make sure everything is synced. When it does that, it checks if it should index a message, by checking their privacy settings inside my database. That call takes ~50 ms, but it will delay the bot startup sometimes for minutes at a time, like it never closes the event loop. If I ctrl+c, it cancels that task and continues onward, if I don't, it takes another X minutes and then switches over eventually and throws a generic error about a task that was never awaited or something like that
I'm not sure where else to make an issue, nobody seems to have the answer, and it is a hard thing to describe.
The text was updated successfully, but these errors were encountered:
I'm not sure if I should make an issue here, or in
discord.py
, but basically I'm using Llama Indexrun-llama
on GitHub, and it usesnest_asyncio
for the event loop patching. Issue is, when I run it alongsidediscord.py
, random things will be put into seemingly random event loops and I'm not sure why? Like for instance when the bot runs startup it checks the guilds it's in and then checks the indexed channels in order to make sure everything is synced. When it does that, it checks if it should index a message, by checking their privacy settings inside my database. That call takes ~50 ms, but it will delay the bot startup sometimes for minutes at a time, like it never closes the event loop. If I ctrl+c, it cancels that task and continues onward, if I don't, it takes another X minutes and then switches over eventually and throws a generic error about atask that was never awaited
or something like thatI'm not sure where else to make an issue, nobody seems to have the answer, and it is a hard thing to describe.
The text was updated successfully, but these errors were encountered: