-
Notifications
You must be signed in to change notification settings - Fork 252
[Misc] Merge diffusion forward context #582
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| yield | ||
| finally: | ||
| _forward_context = prev_context | ||
| get_cached_compilation_config.cache_clear() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove invalid cache_clear call on forward context teardown
override_forward_context calls get_cached_compilation_config.cache_clear() when exiting (lines 72-75), but get_cached_compilation_config is now a plain function without an lru_cache, so it has no cache_clear attribute. Any use of set_forward_context/override_forward_context will raise AttributeError on exit, aborting model initialization and tests immediately. Please restore caching or drop the cache_clear call.
Useful? React with 👍 / 👎.
|
cc @wtomin |
|
resolve the conflict please since #597 merged |
done. |
Signed-off-by: iwzbi <[email protected]>
Purpose
There are 2 omni_diffusion_config context now, simplify into one. Remove
_current_omni_diffusion_configindata.pyand use_forward_contextinforward_context.pyfor all.However, there is an exception: when using vllm components, and vllm internally calls
get_current_vllm_config, but vllm-omni does not explicitly callset_current_vllm_config, therefore internally vllm cannot obtain the correct config.