Skip to content

Conversation

@iwzbi
Copy link
Contributor

@iwzbi iwzbi commented Jan 2, 2026

Purpose

There are 2 omni_diffusion_config context now, simplify into one. Remove _current_omni_diffusion_config in data.py and use _forward_context in forward_context.py for all.
However, there is an exception: when using vllm components, and vllm internally calls get_current_vllm_config, but vllm-omni does not explicitly call set_current_vllm_config, therefore internally vllm cannot obtain the correct config.

@iwzbi iwzbi requested a review from hsliuustc0106 as a code owner January 2, 2026 14:42
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a 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".

Comment on lines 72 to 75
yield
finally:
_forward_context = prev_context
get_cached_compilation_config.cache_clear()

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

@ZJY0516
Copy link
Collaborator

ZJY0516 commented Jan 2, 2026

cc @wtomin

@ZJY0516 ZJY0516 requested review from SamitHuang and ZJY0516 January 2, 2026 15:17
@ZJY0516 ZJY0516 added the ready label to trigger buildkite CI label Jan 2, 2026
@hsliuustc0106
Copy link
Collaborator

resolve the conflict please since #597 merged

@david6666666 david6666666 mentioned this pull request Jan 4, 2026
5 tasks
@iwzbi
Copy link
Contributor Author

iwzbi commented Jan 4, 2026

resolve the conflict please since #597 merged

done.

Signed-off-by: iwzbi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready label to trigger buildkite CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants