mirror/gradio
2
0
Fork 0
mirror of https://github.com/gradio-app/gradio.git synced 2025-04-06 12:30:29 +08:00
Code Issues Packages Projects Releases Wiki Activity

Call run_extra_startup_events in Lite (#10000)

Browse Source 
* Call run_extra_startup_events in Lite

* add changeset

* add changeset

* add changeset

* Use asyncio.create_task() instead

---------

Co-authored-by: gradio-pr-bot <gradio-pr-bot@users.noreply.github.com>
This commit is contained in:
Yuichiro Tachibana (Tsuchiya) 2024-11-21 10:40:51 +09:00 committed by GitHub
parent 0879be78b3
commit 29cfc03ecf
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
.changeset/purple-bugs-see.md Normal file
View File

@ -0,0 +1,5 @@
---
"gradio": patch
---
fix:Call `run_extra_startup_events` in Lite

5
gradio/blocks.py
View File

@ -1,5 +1,6 @@
from __future__ import annotations
import asyncio
import copy
import dataclasses
import hashlib
@ -2532,6 +2533,10 @@ Received inputs:
# In contrast, in the Wasm env, we can't do that because `threading` is not supported and all async tasks will run in the same event loop, `pyodide.webloop.WebLoop` in the main thread.
# So we need to manually cancel them. See `self.close()`..
self.run_startup_events()
# In the normal mode, self.run_extra_startup_events() is awaited like https://github.com/gradio-app/gradio/blob/2afcad80abd489111e47cf586a2a8221cc3dc9b6/gradio/routes.py#L1442.
# But in the Wasm env, we need to call the start up events here as described above, so we can't await it as here is not in an async function.
# So we use create_task() instead. This is a best-effort fallback in the Wasm env but it doesn't guarantee that all the tasks are completed before they are needed.
asyncio.create_task(self.run_extra_startup_events())
self.is_sagemaker = (
False # TODO: fix Gradio's behavior in sagemaker and other hosted notebooks