TGTGInsighttelegram intelligenceLIVE / telegram public index
← Python Заметки
Назад кон каналите

TGINSIGHT SIMILAR POSTS

Најди сличен содржај

Изворен канал @pythonotes · Post #400 · 8 дек.

Погледај објаваПогледај оригинал

Три способа выполнить множество задач с asyncio Функция для примера: async def do_it(n): await asyncio.sleep(random.uniform(0.5, 1)) return n 1. Последовательный вызов async def main(): for i in range(100): result = await do_it(i) Такой вызов имеет смысл только тогда, когда результат одной задачи требуется для вызова следующей. Если они независимы, то это антипаттерн, так как аналогичен простому синхронному вызову по очереди. 2. Упорядоченный результат async def main(): tasks = [do_it(i) for i in range(100)] results = await asyncio.gather(*tasks) Выполняет корутины конкурентно и возвращает результат в виде списка. Полезен когда требуется получить результаты в том же порядке в котором задачи отправлены. 3. Результат по мере готовности tasks = [asyncio.create_task(do_it(i)) for i in range(100)] for cor in asyncio.as_completed(tasks): result = await cor Так же выполняет корутины конкурентно, но не гарантирует порядок. Результат возвращается по мере готовности, каждый отдельно. Полезен когда нужно обработать любой ответ как можно скорее. #async

Hashtags

#async
Резултати

Пронајдени 14 слични објави

Пребарај: #downtime

当前筛选 #downtime清除筛选
Luckydonalds Bots: Development/Status

@luckydonaldsbots · Post #162 · 21.10.2018 г., 13:20

Најди сличноПогледај

Apperently also @anonymize_bot is affected. Currently looking into the issue. Update: It should now be back and running, but telegram reports about two thousand updates being still unprocessed, but that is decreasing. It will recover soon, bear with me, it works as fast as telegram allows it to. Update: @anonymize_bot It is now back to normal. #Anonymize#downtime'

Hashtags

#anonymize#downtime
Luckydonalds Bots: Development/Status

@luckydonaldsbots · Post #108 · 29.11.2017 г., 11:39

Најди сличноПогледај

Expected downtime: Today, 13:00 UTC. Duration 1h. Delayed, see post below. Because my current server isn't powerful enough, especially regarding Disk IO speed, I will move part of the infrastructure to a new server with SSD storage. This means I have to take down the databases, and copy them over. I'll try to keep the bots running which doesn't need a database, like @ponbot, @anonymize_bot, @HeyAdminBot, @moustache_bot, etc. #expected_downtime#downtime

Hashtags

#expected_downtime#downtime
Luckydonalds Bots: Development/Status

@luckydonaldsbots · Post #251 · 04.07.2020 г., 14:51

Најди сличноПогледај

Maintenance: Moving @BanWarnBot to the new server. Okey going through the same procedure for @BanWarnBot now, hopefully without the database breaking this time. Turning the bot off for moving the database, so any /warns send in the meantime shouldn't get lost. As soon as it's on the new server it should pick up those, and carry out the needed actions. I'll take @BanWarnBot down in 10 minutes. Other bots should not be affected. #maintenance#downtime#BanWarnBot

Hashtags

#maintenance#downtime#banwarnbot
Luckydonalds Bots: Development/Status

@luckydonaldsbots · Post #188 · 24.02.2019 г., 01:05

Најди сличноПогледај

If you docker refuses to start and sudo service docker status is showing logs like this: Feb 24 01:30:06 hostname dockerd[19544]: time="2019-02-24T01:30:06.718823877+01:00" level=error msg="stream copy error: reading from a closed fifo" It might be that /var/run/docker.sock is a mount in one of your containers. Therefore if that doesn't exist - and only shortly - it will be created as a folder, thus making it impossible for docker to start. Fix it with sudo rmdir /var/run/docker.sock, and sudo service docker start. #TechnicalDetails#downtime#in_progress

Hashtags

#technicaldetails#downtime#in_progress
12
← ПретходнаСтраница 1 од 2Следна →