Skip to content

Coordinate non-interactive library messages through the project logger #14479

Description

@wunianze666-netizen

Problem

A few importable library paths still write warnings or initialization details directly to stdout:

  • VectorQuantizer reports remap configuration with print() in src/diffusers/models/autoencoders/vae.py.
  • WanAnimatePipeline prints when previous-segment conditioning frames are resized.
  • The LongCat image helpers print when caller arguments are ignored.

These messages cannot be controlled through the Diffusers logging configuration and can pollute stdout for library consumers.

Proposed scope

Would maintainers accept one coordinated PR that:

  1. routes these three non-interactive messages through the existing module loggers;
  2. preserves their current severity and wording where practical; and
  3. adds focused caplog regression coverage for each path?

I would intentionally exclude output that is part of an interactive or explicit workflow, such as MagCache calibration results, conversion scripts, and documentation examples.

Coordination and disclosure

I previously opened #13900, #13936, and #13939 as separate one-off changes before following the current AI-assisted contribution workflow. To reduce review load, I am closing those PRs and will wait for explicit maintainer confirmation here before preparing a single pattern-level PR. The audit and proposed implementation are AI-assisted; I will run the repository self-review skill and include the final report and exact test output in any follow-up PR.

cc @yiyixuxu@DN6

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions