Skip to content

fix: add missing f-string prefixes across pipelines and schedulers#13407

Open
Ricardo-M-L wants to merge 1 commit intohuggingface:mainfrom
Ricardo-M-L:fix/missing-fstring-prefixes-pipelines
Open

fix: add missing f-string prefixes across pipelines and schedulers#13407
Ricardo-M-L wants to merge 1 commit intohuggingface:mainfrom
Ricardo-M-L:fix/missing-fstring-prefixes-pipelines

Conversation

@Ricardo-M-L
Copy link
Copy Markdown

Summary

Add missing f prefix to ~50 string literals where variables like {self.__class__}, {self.config}, {unet.config.*}, {type(...)} are printed as literal text instead of being interpolated.

Categories fixed:

  • Safety checker messages with {self.__class__} (~46 pipeline files)
  • Scheduler config messages with {self.config} (2 instances)
  • DeepFloyd IF messages with {unet.config.*} (3 files)
  • Pipeline loading utils with {StableDiffusionInpaintPipelineLegacy} (1 instance)
  • Wan VACE pipeline with {type(reference_images)} (2 instances)

Motivation

Without the f prefix, log/warning messages show literal {self.__class__} text instead of actual class names, making debugging and user experience worse.

Test plan

  • Verify warning messages correctly show actual class/config values

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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