Yuichiro Tachibana (Tsuchiya)

@freddyaboulton Thanks, is it this? https://github.com/gradio-app/gradio/pull/7855/files#diff-704d0432232d65a5a81503f0e97f31053a3826e4e291fd3920eb24d1bb5d4e3aR50

@pngwn Can you approve this PR if you are ok because the merge is blocked?

Removed some steps from the `deploy-spaces` workflow as the same steps are done in the `install-all-deps` action, as @pngwn suggested. Looks like the workflow ran correctly: https://github.com/gradio-app/gradio/actions/runs/8887216886/job/24402132060

The direct reason of the E2E test failure (timeout) is that the Lite app didn't boot up successfully with an error caused by the [change on `synchronize_async()`](https://github.com/gradio-app/gradio/pull/7850/files#diff-5557f3070c89abd91ce70a262a2f7df99867027634a451c96102392e4d81d9d2R844). In the Wasm/Pyodide...

I also found when the system is set as dark-mode, the Gradio Playground is initialized in light-mode during the initial load, but becomes dark after the initialization finishes. ![CleanShot 2024-03-25...

@aliabd Thank you, I checked the changes and confirmed it has nice look and feel! I left one comment. I think it's technically a bug but not critical so we...

@abidlabs > Can we just make this the default? Is there any downside of using shared-worker by default? Yea, that's an option. On the other hand, these are what I...

Yes, definitely. Will write it.

Added a section about SharedWorker: #7923 Update: Merged it to this PR.

I think Lite's E2E tests should be run on a separate CI job because the functional tests take a long time and randomly fail.