Skip to content
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

fix lora switch #1143

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix lora switch #1143

wants to merge 1 commit into from

Conversation

frc99
Copy link

@frc99 frc99 commented Nov 18, 2024

fix lora cannot switch with controlnet, see more in #1141

Summary by CodeRabbit

  • New Features

    • Updated the method for obtaining the model reference to enhance compatibility with the current framework.
  • Bug Fixes

    • Improved the handling of model weights and Conv2d layers for better performance with the OneFlow backend.

Copy link
Contributor

coderabbitai bot commented Nov 18, 2024

Walkthrough

The changes in this pull request involve modifications to the onediff_lora.py file, specifically within the HijackLoraActivate class. A new import statement for onediff_shared is added, and the method for obtaining the sd_model is updated to use onediff_shared.current_unet_graph.graph_module instead of the previous method. The logic in the activate function remains mostly unchanged, but the assignment of onediff_sd_model reflects the new source. The functionality related to module weight application and backend handling is preserved.

Changes

File Change Summary
onediff_sd_webui_extensions/onediff_lora.py Added import for onediff_shared and modified hijacked_activate function to change sd_model source.

Poem

In the code where rabbits play,
A new path found, a brighter way.
With shared models now in sight,
We hop along, all feels just right!
We tweak and tune, with joyful cheer,
For every change, we hold so dear. 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
onediff_sd_webui_extensions/onediff_lora.py (1)

42-44: Document the architectural change

The switch from parameter-based model access to using onediff_shared.current_unet_graph represents a significant architectural change. Please add a comment explaining:

  1. Why this change was necessary for fixing the LoRa switching issue
  2. How current_unet_graph is managed throughout its lifecycle
  3. Any considerations for future maintainers

Add a comment like:

+        # Using global graph module instead of p.sd_model to ensure consistent
+        # model reference during LoRa switching with ControlNet (fixes #1141)
         sd_model = onediff_shared.current_unet_graph.graph_module
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 424c81a and 596f717.

📒 Files selected for processing (1)
  • onediff_sd_webui_extensions/onediff_lora.py (2 hunks)
🔇 Additional comments (2)
onediff_sd_webui_extensions/onediff_lora.py (2)

2-4: LGTM: Import changes are appropriate

The addition of onediff_shared import is necessary for the new model access method and is properly placed in the import section.


42-44: Verify thread safety of global model reference

The change from using a parameter-based model reference (p.sd_model.model.diffusion_model) to a global reference (onediff_shared.current_unet_graph.graph_module) might introduce thread safety concerns in concurrent scenarios.

Let's check if there are any concurrent access patterns:

✅ Verification successful

Based on the gathered information, I can now provide the final response:

Thread safety concerns are mitigated by SD WebUI's execution model

The global current_unet_graph is used within a controlled context where:

  • It's initialized once at module import time
  • Model switching and compilation happen in a sequential manner through SD WebUI's pipeline
  • The graph module is swapped atomically during model initialization
  • No concurrent modification patterns were found in the codebase

The change from parameter-based to global reference is safe in this context as SD WebUI processes requests sequentially by design.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any concurrent processing or threading related code
rg -l "Thread|threading|concurrent|asyncio|multiprocessing" 

# Check how current_unet_graph is managed
ast-grep --pattern 'current_unet_graph = $_'

Length of output: 518


Script:

#!/bin/bash
# Let's check the OneDiffCompiledGraph implementation and usage
ast-grep --pattern 'class OneDiffCompiledGraph'

# Check where current_unet_graph is accessed/modified
rg "current_unet_graph" -A 3

# Check if there are any locks or synchronization mechanisms
rg "Lock|Semaphore|RLock|mutex"

Length of output: 4728


Script:

#!/bin/bash
# Let's check the OneDiffCompiledGraph class definition and its usage pattern
cat onediff_sd_webui_extensions/onediff_shared.py

# Check the context where the graph module is used
rg -B 3 "graph_module" onediff_sd_webui_extensions/scripts/onediff.py

# Look for any initialization or setup code
ast-grep --pattern 'def setup($$$)'

Length of output: 728

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant