Skip to content

Conversation

psychedelicious
Copy link
Collaborator

Summary

If incompatible LoRAs are added, prevent Invoking.

The logic to prevent adding incompatible LoRAs to graphs already existed. This does not fix any generation bugs; just a visual inconsistency where it looks like Invoke would use an incompatible LoRA.


I also slightly refactored how the readiness check args are passed in to use a single object. Much harder to accidentally pass the wrong thing in this way.

Related Issues / Discussions

https://discord.com/channels/1020123559063990373/1149506274971631688/1410666884306571396

QA Instructions

n/a

Merge Plan

n/a

Checklist

  • The PR has a short but descriptive title, suitable for a changelog
  • Tests added / updated (if applicable)
  • Documentation added / updated (if applicable)
  • Updated What's New copy (if doing a release after this PR)

@github-actions github-actions bot added the frontend PRs that change frontend files label Aug 29, 2025
@psychedelicious psychedelicious enabled auto-merge (rebase) September 1, 2025 04:37
If incompatible LoRAs are added, prevent Invoking.

The logic to prevent adding incompatible LoRAs to graphs already
existed. This does not fix any generation bugs; just a visual
inconsistency where it looks like Invoke would use an incompatible LoRA.
@psychedelicious psychedelicious force-pushed the psyche/feat/ui/lora-readiness-checks branch from 0dcd23b to 1da6c3d Compare September 1, 2025 04:37
@psychedelicious psychedelicious merged commit 3c9c49f into main Sep 1, 2025
13 checks passed
@psychedelicious psychedelicious deleted the psyche/feat/ui/lora-readiness-checks branch September 1, 2025 04:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
frontend PRs that change frontend files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants