coro | Small coroutine/ '' protothread '' -with-a-stack header | Android library

Your code seems to suggest that it is okay to have two instances of threadable running concurrently, at least for some overlap period and that you unconditionally want to run a a new instance of threadable after 3600 seconds has expired. That's all I can go on and based on that my only suggestion is that you might consider switching to using the multiprocessing.pool.Pool class as the multiprocessing pool, which has the advantage of (1) it is a different class than what you have been using as for no other reason is likely to produce a different result and (2) unlike the ProcessPoolExecutor.shutdown method, the Pool.terminate method will actually terminate running jobs immediately (the ProcessPoolExecutor.shutdown method will wait for jobs that have already started, i.e. pending futures, to complete even if you had specified shutdown(wait=False), which you had not).

The equivalent code that utilizes multiprocessing.pool.Pool would be:

asyncio.wait() returns a tuple. you must unpack it like so:

There's no need for you to put the hexcolor value in quotes

From the discord dev docs:

CHAT_INPUT command names and command option names must match the following regex ^[\w-]{1,32}$

The regex essentially translates to:

If there is a lowercase variant of any letters used, you must use those

In this case, your option name, 'Command' has an uppercase 'C', which is disallowed.

Note: The length of the name must also be lower or equal to 32.

Application command naming

If it's not the bandwidth that limits you (but I cannot check this), there is a solution less complicated than the celery and rabbitmq but it is not as scalable as the celery and rabbitmq, it will be limited by your number of CPU.

Instead of splitting calls on celery workers, you split them on multiple processes.

I modified the fetch function like this:

It's all note : when you use function get_db_session in database.py like a generator, close function of session doesn't work as auto, so you should close them like manually. If you need more detail, send email, drr000t3r@gmail.com. Good Luck.

database.py

Looks like it should work now.. I see, its added to the officially supported built-in packages.

https://github.com/pyodide/pyodide/tree/main/packages

This implementation allows for any member of the guild to simply type !dm in any channel, and the bot will message the user-specified in client.get_user() a message

This error is being generated by passing an key with a value of None in overwrites. It's probably admin_role. You can check:

• You actually have a role named Admin on the guild;
• You have activated guild intents so that you can have the list of roles.