Open
Conversation
feat: optimize webui process management and gradio compatibility
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR applies a minimal fix to the WebUI initialization logic to ensure compatibility with recent Gradio versions.
Specifically, it removes deprecated
concurrency_countusage inBlocks.queue()and aligns the launch behavior with the current Gradio API.Motivation
Recent versions of Gradio raise a
DeprecationWarning(and fail execution in strict environments) whenconcurrency_countis passed toqueue().This change prevents WebUI startup failure without affecting any training, inference, or UI logic.
Scope of Change
Safety
This change is intentionally minimal and scoped only to WebUI startup.
It should be safe to merge without introducing side effects.
Environment