Dispatcher

Send your data to separate processes. I used concurrent.futures because I like the simple interface.

This runs in about 11 seconds on my computer.

I'm not familiar with Discord bots but I don't think your endHandler will ever run the else if part the way it is because your code is always creating a new dispatcher when it plays the next song, but never sets up a finish handler for it.

This is exactly the reason why coroutines were invented and how they differ from threaded concurrency. Coroutines don't block, but suspend (well, they can do both). And "suspend" isn't just another name for "block". When they suspend (e.g. by invoking join()), they effectively free the thread that runs them, so it can do something else somewhere else. And yes, it sounds like something that is technically impossible, because we are in the middle of executing the code of some function and we have to wait there, but well... welcome to coroutines :-)

You can think of it as the function is being cut into two parts: before join() and after it. First part schedules the background operation and immediately returns. When background operation finishes, it schedules the second part on the main thread. This is not how coroutines works internally (functions aren't really cut, they create continuations), but this is how you can easily imagine them working if you are familiar with executors or event loops.

delay() is also a suspending function, so it frees the thread running it and schedules execution of the code below it after a specified duration.

What can I do to ensure that it's only called once?

Nothing, that's how it's meant to work. In the View system you would not ask "Why is my view invalidated 3 times?". The framework invalidates (recomposes) the view as it needs, you should not need to know or care when that happens.

The issue with your code is that your Composable is reading the old value from preferences, that is not how it should work, that value should be provided by the viewmodel as part of the state. Instead of providing just the new price, expose a Data Class that has both the new and old price and then use those 2 values in your composable to determine what color to show, or expose the price and the color to use.

As thethiny already pointed out, chatmember updates have so associated message: update.message will be None, while update.chat_member will be an instance of ChatMemberUpdated. Note that Message.reply_text is just a shortcut for Bot.send_message(chat_id=message.chat.id, ...), so as long as you have the chat_id you can just use e.g. context.bot.send_message - and you can get that chat_id from ChatMemberUpdated.chat. In fact, you can still use PTBs shortcuts, e.g. update.effective_chat.send_message.

Please check out the docs of

• ChatMemberUpdated (official and PTB)
• Update.effective_chat
• Chat.send_message

as well as the chatmemberbot.py example provided by PTB.

Disclaimer: I'm currently the maintainer of python-telegram-bot

The ajax calls normally are suitable for handing responses like JSON, XML than views. So, If you change your controller to @RestContoller from @Controller, this should work.

One idea could be to return the Job in method1 like the following:

I don't think MutableState is designed to be used in the ViewModel layer, since it's an observable integrated with the compose runtime. You could create a MutableStateFlow instead and use collectAsState() from the view layer.

In your case the issue is probably, because of the state is captured in a coroutine invoked outside composition.

This issue is solved after correcting up my code