A community member is trying to use the DiscordReader and is encountering a "RuntimeError: This event loop is already running" issue. Another community member suggests using the example notebook, but the original poster says they weren't using it. The solution of using nest_asyncio.apply() seems to have worked for the original poster.
The discussion then shifts to the challenges of using async capabilities with the Discord reader, as it was designed for synchronous use. The community members discuss the possibility of adding async capabilities to the Discord reader to make it more useful for Discord bots that need to summarize channel contents.
There is also a discussion around the expiration of the Discord token, and the need to regularly run the import process to continuously load conversations into the Llama Index.
@jerryjliu0 I made a discordbot that has async methods, trying to use an on_message seems to make it quit with the nest_asyncio.apply and if I don't have that then I'll get the event loop exception, is there an easy fix?
Yeah I see. Our discord reader is honestly pretty hacky (it was designed for synchronous use, and discord's api is entirely async). I'm open to adding methods on the Discord reader that would allow it to make use of native async capabilities
Ah I see yeah I wanted to make a discord bot that could summarize the contents of a channel if people didn't feel like reading all of a convo I feel like the discord reader would be more useful with async capabilities since people might want to use it with the discord api more
I am planning to load conversions into Llama Index continuously, so I would have to run import on regular basis to achieve that? (I am not a dev, hence the noobie questions)
